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
Update default precision step, modulo tests #5908
Conversation
@@ -34,6 +34,16 @@ org.apache.lucene.index.IndexWriter#forceMergeDeletes(boolean) @ use Merges#forc | |||
@defaultMessage QueryWrapperFilter is cachable by default - use Queries#wrap instead | |||
org.apache.lucene.search.QueryWrapperFilter#<init>(org.apache.lucene.search.Query) | |||
|
|||
@defaultMessage Pass the precision step from the mappings explicitly instead | |||
org.apache.lucene.search.NumericRangeQuery#newDoubleRange(java.lang.String,java.lang.Double,java.lang.Double,boolean,boolean) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
man those seem to be trappy - maybe we should deprecate them in Lucene as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left some comments - looks good to me so far.... |
…of what precision_step is
… fieldtype (for futureproofing)
OK, I think this is ready. One change i made: was to actually set the precisionStep in the fieldType passed to Lucene. This was just for consistency, so if something like https://issues.apache.org/jira/browse/LUCENE-5605 happens, it wont break. |
LGTM please squash and push to |
See #5905