You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2013/06/19 21:21:19 UTC
[jira] [Created] (LUCENE-5069) Can/should we store NumericField's
precisionStep in the index?
Michael McCandless created LUCENE-5069:
------------------------------------------
Summary: 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org