Alternative to ElasticSearch

[shua123]

We currently run a very old version of ElasticSearch using a retired gem. We have a lot of stability issues keeping ElasticSearch running. When it goes down it interrupts search functionality and worse affects signups and form submissions from saving in the database (Issue #154). At the moment, the majority of our current searching use does not need the full power of ElasticSearch.

Some alternatives:

• Ransack: https://github.com/activerecord-hackery/ransack
• Filterrific: http://filterrific.clearcove.ca
• PG Search: https://github.com/Casecommons/pg_search

Immediate Goal: Determine if there is an alternative we switch to in the short term to be able to get away from the ancient ElasticSearch setup immediately. Towards this goal I have been testing out Ransack. It is easy to implement without changing much of our existing code.

[cromulus]

I just implemented pg_search and really like it. requires a bit of fiddling
up front, but it's super fast, you don't have to run another daemon and it
integrates directly into active record in a way that is very intuitive.

Similarly, I'm a huge fan of ransack, however, it doesn't do well
performance-wise for fulltext. If you are searching attributes on rows,
though, it's the best.

I could foresee a combination of the two, ransack for attributes and
pg_search for notes, submissions, etc.

I'd also like to switch our tagging system to acts_as_taggable, which has
it's own built in tag search which is really awesome and powerful.

On Fri, Sep 9, 2016 at 2:22 PM, Josh Kalov [email protected] wrote:

We currently run a very old version of ElasticSearch using a retired gem.
We have a lot of stability issues keeping ElasticSearch running. When it
goes down it interrupts search functionality and worse affects signups and
form submissions from saving in the database (Issue #154
#154). At the moment, the
majority of our current searching use does not need the full power of
ElasticSearch.

Some alternatives:

• Ransack: https://github.com/activerecord-hackery/ransack
• Filterrific: http://filterrific.clearcove.ca
• PG Search: https://github.com/Casecommons/pg_search

Immediate Goal: Determine if there is an alternative we switch to in the
short term to be able to get away from the ancient ElasticSearch setup
immediately. Towards this goal I have been testing out Ransack. It is easy
to implement without changing much of our existing code.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#196, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAMobH_0FDa21P89KLKbEgKfjUVNlezks5qoaPRgaJpZM4J5UkU
.

[shua123]

@cromulus So you made the switch to postgres for pg_search?

[cromulus]

Another project

On Sep 9, 2016 2:40 PM, "Josh Kalov" [email protected] wrote:

@cromulus https://github.com/cromulus So you made the switch to
postgres for pg_search?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#196 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAMoVby05oWXa-_KijvTN0BDqlZh6Kmks5qoagLgaJpZM4J5UkU
.

[shua123]

Search page options:

• Remove first and last name searches. Keep Full name
• Zip Code starts with
• Zip Code does not starts with?
• Move Address_1 to hidden section? (not now)
• Remove secondary device & connections from search
• Add select multiple for participation type

Show additional options:

• Not verified?
• Form submission content
• Active/inactive (is there a submission) (Future)

Column 1	Column 2	Column 3
Name	Primary device + description	Tag
Email	Primary connection + description	Participation Type
Phone Number		gift card
Address		Additional Options
Zip
Preferred Contact Method

---

Results List

• Remove Ward
• Change Phone number to display without +sign (check this in csv export and other places too)
• "Active" is there a submission for a person? (Future)
• Potential duplicate? (Future)