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

"rake db:migrate db:seed" elasticsearch error #111

Open
fuyuasha opened this issue Dec 16, 2015 · 7 comments
Open

"rake db:migrate db:seed" elasticsearch error #111

fuyuasha opened this issue Dec 16, 2015 · 7 comments

Comments

@fuyuasha
Copy link

Any suggestions (using elasticsearch 2.1.0_1)?

[ERROR] There has been an error when creating the index -- elasticsearch returned:
400 : {"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"Mapping definition for [key_ids] has unsupported parameters: [as : commits_keys.pluck(:key_id)]"}],"type":"mapper_parsing_exception","reason":"Failed to parse mapping [commit]: Mapping definition for [key_ids] has unsupported parameters: [as : commits_keys.pluck(:key_id)]","caused_by":{"type":"mapper_parsing_exception","reason":"Mapping definition for [key_ids] has unsupported parameters: [as : commits_keys.pluck(:key_id)]"}},"status":400}
[ERROR] There has been an error when creating the index -- elasticsearch returned:
400 : {"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"Mapping definition for [index_in_section] has unsupported parameters: [as : send(:key).index_in_section]"}],"type":"mapper_parsing_exception","reason":"Failed to parse mapping [translation]: Mapping definition for [index_in_section] has unsupported parameters: [as : send(:key).index_in_section]","caused_by":{"type":"mapper_parsing_exception","reason":"Mapping definition for [index_in_section] has unsupported parameters: [as : send(:key).index_in_section]"}},"status":400}

@RISCfuture
Copy link
Contributor

I've seen this too. Seems to be related to a newer version of ElasticSearch. If you find out more let me know, but at some point we should probably switch to Chewy.

@fuyuasha
Copy link
Author

Ah OK, uninstalled elasticsearch 2.1.0_1 and installed elasticsearch-0.20.6.tar.gz per https://github.com/karmi/retire - no more errors and things seem to be working.

Thanks

@yunussasmaz
Copy link
Contributor

Yeah, it's a version problem. ElasticSearch 2.x deprecated a few things we are using. We are on ElasticSearch 1.2 at Square.

@fuyuasha
Copy link
Author

OK ElasticSearch 1.2 - I'll use that - thanks for the update.

@fuyuasha
Copy link
Author

Can I ask what version of rails is Square using for shuttle, I'm having some other problems and wonder if that might be the cause, I'm using:
rails (4.0.9)
rails-observers (0.1.2)

@yunussasmaz
Copy link
Contributor

That's what we have, too: https://github.com/square/shuttle/blob/master/Gemfile.lock.

@fuyuasha
Copy link
Author

Oh yep - I forget it's installed (and versioned) via the Gemfile.

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

No branches or pull requests

3 participants