Searchkick Elasticsearch抛出400错误

时间:2017-12-11 17:45:11

标签: ruby-on-rails ruby elasticsearch searchkick

我最近更新到High Seirra,不确定这是否意味着什么,我现在在尝试重新索引Active Record Model时遇到此错误。

我尝试过的事情。我重新安装了RVM,Ruby,Elasticsearch。仍然得到相同的错误。

我团队中的其他人做了同样的升级,他们运行得很好。 以下是我得到的错误。

Elasticsearch::Transport::Transport::Errors::BadRequest: [400] {"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"Failed to parse mapping [_default_]: Could not convert [word_start.index] to boolean"}],"type":"mapper_parsing_exception","reason":"Failed to parse mapping [_default_]: Could not convert [word_start.index] to boolean","caused_by":{"type":"illegal_argument_exception","reason":"Could not convert [word_start.index] to boolean","caused_by":{"type":"illegal_argument_exception","reason":"Failed to parse value [analyzed] as only [true] or [false] are allowed."}}},"status":400}
from /Users/rrobin244/.rvm/gems/ruby-2.3.3/gems/elasticsearch-transport-5.0.4/lib/elasticsearch/transport/transport/base.rb:202:in `__raise_transport_error'

2 个答案:

答案 0 :(得分:4)

检查您的Gemfile.lock并在此处检查elasticsearch的版本。如果它与本地系统中的elasticsearch版本不匹配,请删除gemfile.lock文件并运行捆绑软件。这为我解决了这个问题。

答案 1 :(得分:0)

我有同样的问题,我不得不升级我的Mac上的elasticsearch

brew upgrade elasticsearch