You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to the discussion in #144 , is it possible to change the error message to be much more succinct/clear about the reason for the failed insert? In my case, it wasn't a uppercase index problem, but a template type problem. I ended up having to delete the the template and all indicies using it in order to be able to insert again. It would great if this error log could be:
~1 line long
provide clarity around why the insert failed (index has caps, type mismatch on field X, etc)
Reccomended way to solve (ensure no caps in index, run "XYZ" to update template type if desired, etc)
@jordansissel
Similar to the discussion in #144 , is it possible to change the error message to be much more succinct/clear about the reason for the failed insert? In my case, it wasn't a uppercase index problem, but a template type problem. I ended up having to delete the the template and all indicies using it in order to be able to insert again. It would great if this error log could be:
For reference:
ES Version:
{ "status" : 200, "name" : "Torso", "cluster_name" : "elasticsearch", "version" : { "number" : "1.6.0", "build_hash" : "cdd3ac4dde4f69524ec0a14de3828cb95bbb86d0", "build_timestamp" : "2015-06-09T13:36:34Z", "build_snapshot" : false, "lucene_version" : "4.10.4" }, "tagline" : "You Know, for Search" }
Logstash version:
# /opt/logstash/bin/logstash -V
logstash 1.5.4
The text was updated successfully, but these errors were encountered: