[
https://issues.apache.org/jira/browse/LUCENE-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688355#comment-13688355
]
Adrien Grand commented on LUCENE-5069:
--------------------------------------
bq. While indexing, adding a new item with different step should also fail.
+1 This motivation is enough to me to store the precision step in the field
info.
> Can/should we store NumericField's precisionStep in the index?
> --------------------------------------------------------------
>
> Key: LUCENE-5069
> URL: https://issues.apache.org/jira/browse/LUCENE-5069
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Michael McCandless
>
> I was just helping a user (buzzkills) on IRC on why NumericRangeQuery was
> failing to hit the expected docs ... and it was because s/he had indexed with
> precStep=4 but searched with precStep=1.
> Then we wondered if it'd be possible to somehow catch this, e.g. we could
> maybe store precStep in FieldInfo, and then fail at search time if you use a
> "non-matching" precStep?
> I think you can index fine and then search on a multiple of that? E.g., I
> can index with precStep=2 but search with precStep=8? But indexing with
> precStep=4 and searching precStep=1 won't work ...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
