[
https://issues.apache.org/jira/browse/LUCENE-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe resolved LUCENE-2544.
---------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 4.1)
Lucene Fields: (was: New)
Given the fact that this just provides sugar over existing functionality, and
considering [~thetaphi]'s objections, and the two years with zero activity,
resolving as Won't Fix.
> Add 'divisor' to NumericField, allows for easy storage of full precision
> data, but indexing *starting* at lower precision.
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-2544
> URL: https://issues.apache.org/jira/browse/LUCENE-2544
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/other
> Affects Versions: 3.0.2
> Reporter: Woody Anderson
> Priority: Minor
> Attachments: LUCENE-2544.patch
>
>
> In some cases, we want to index a timestamp or some other high precision
> numeric at a much lower precision, but we still want to store the full
> precision data.
> Rather than have to do this with two Field objects in the Document, it'd be
> easier to provide NumericField with a divisor as well as prevision step. The
> divisor would apply before beginning the trie logic.
> most often, this is a divide by 1, but that will happen only during the
> constructor or setXXXValue() in NumericTokenStream.
> I have the patch for this, or i will after i isolate it.
--
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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
