Netflix / inviso

Other
205 stars 65 forks source link

Can't run inviso with elastic search 2.3.2 #12

Open othman-essabir opened 8 years ago

othman-essabir commented 8 years ago

Hello folks,

I'm trying to run inviso with elastic search 2.3.2. While trying to run this command: curl -XPUT http://localhost:9200/inviso -d @inviso/elasticsearch/mappings/config-settings.json

I get the following error:

{"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"Mapping definition for [_timestamp] has unsupported parameters: [store : true]"}],"type":"mapper_parsing_exception","reason":"Failed to parse mapping [default]: Mapping definition for [_timestamp] has unsupported parameters: [store : true]","caused_by":{"type":"mapper_parsing_exception","reason":"Mapping definition for [_timestamp] has unsupported parameters: [store : true]"}},"status":400}

How can we adjust inviso in order to have it compatible with elastic search 2.3.2 ?

danielcweeks commented 8 years ago

@othman-essabir it looks like timestamp is deprecated in ES 2.0+

See here: https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-timestamp-field.html

I'm not clear how much of an impact this would have, because it may rely on this field being stored. You could try removing that property definition and see if it works because we are setting the '_timestamp' explicitly when indexed and it should behave just like any other property.

tglstory commented 8 years ago

We just removed the "store": true line, and it seems to work. You do have to remove all dots in your field names though; I do that in the jes component where I bulk to the ES cluster.