[
https://issues.apache.org/jira/browse/LUCENE-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012727#comment-13012727
]
Ryan McKinley commented on LUCENE-3001:
---------------------------------------
The default precisionStep should not have to have to be standardized -- solr
can always set it in the constructor.
The real issue is how to deal with binary vs text stored fields. We could
either:
1. Add a binary option to the constructor so the stored value is either text or
binary
2. Standardize on binary and have easy ways to pull it out directly from lucene
Seems option #1 has the most flexibility and least impact on existing pure
lucene NumericField users
> Add TrieFieldHelper lucene so we can write solr compatible Trie* fields w/o
> solr dependency
> -------------------------------------------------------------------------------------------
>
> Key: LUCENE-3001
> URL: https://issues.apache.org/jira/browse/LUCENE-3001
> Project: Lucene - Java
> Issue Type: New Feature
> Reporter: Ryan McKinley
> Priority: Minor
> Attachments: LUCENE-3001-TrieFieldHelper.patch
>
>
> The solr support for numeric fields writes the stored value as binary vs the
> lucene NumericField
> We should move this logic to a helper class in lucene core so that libraries
> that do not depend on solr can write TrieFields that solr can read.
--
This message is automatically generated by JIRA.
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
