Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update ElasticSearch version #154

Closed
smarziano opened this issue Feb 4, 2016 · 4 comments
Closed

Update ElasticSearch version #154

smarziano opened this issue Feb 4, 2016 · 4 comments

Comments

@smarziano
Copy link
Member

Currently we are using a very outdated version of ElasticSearch and sometimes search will stop working. We want to update to the most recent of ElasticSearch.

This issue relates to other ElasticSearch issues #72 and #73

@shua123
Copy link
Contributor

shua123 commented Apr 15, 2016

Experimentation!

We are running ElasticSearch v0.20.6 with the Tire ("retire") gem.
I installed and tested v2.13.x, v1.7.5, and v0.90.13. With all of them, Elasticsearch did not like the submissions part and would fail indexing for persons with associated submissions.

MapperParsingException[failed to parse [submissions]]; nested: IllegalArgumentException[unknown property [submission_values]];

So I think we need to switch from Tire to elasticsearch-rails before enabling a new version of elasticsearch.

@cromulus I know you were looking at some search stuff. If you want to tackle replacing Tire before we get a chance to do it feel free to do so.

@cromulus
Copy link
Contributor

@shua123 I'm running 2.3.1 on production and now in the vagrant box. I did some updates to the code to cleaned it up a bit.

That said, looking into elasticsearch-rails, the interface isn't all that different. We probably could swap it out fairly easily.

I haven't had a chance to test the submissions bits. Let me see if I can figure that out.

@smarziano
Copy link
Member Author

Making this a high priority item. This is happening too often and is really making test management difficult.

@smarziano
Copy link
Member Author

Closing this issue since we switched to ransack.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants