Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Timestamp index settings incorrectly stored #3174
When setting a timestamp field as not indexed, the value is not saved correctly in the cluster state.
Using the following index template:
Creating a new index (foo-test) with that template works correctly. The mapping returned is as follows:
Notice that the values for the timestamp field now uses boolean values instead of yes/no.
The index setting on the timestamp field works correctly on 0.20.0RC1. The biggest change is the toXContent method. The build sets the fields as a boolean: builder.field("index", fieldType.indexed()), which works on other field mappers.
I have not ran the test in a debugger yet, but will do so shortly.
The timestamp field in 0.20.0RC1
The fix should be setting the field as:
Can submit a pull request, but it's a one line change. :) Will do so anyways later on. This issue probably affects the RoutingFieldMapper as well.
This issue is one of those times when the test case will be much longer than the fix.:)
I will attempt do have a PR shortly. This feature is not essential in my system and I am in the middle of a Lucene 4.3/elasticsearch 0.90 upgrade. However, if 0.90.2 will be released soon, I will work on it first. Any word on its release?