[
https://issues.apache.org/jira/browse/LUCENE-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012723#comment-13012723
]
Uwe Schindler commented on LUCENE-3001:
---------------------------------------
bq. EG we can record that "this field is a NumericField" and store it in binary
format.
We have lots of unused bits in the index format for the type (compressed...). A
numeric field is nothing different from a string or binary field in the
underlying index format, all are byte[] in trunk. String uses an utf8 decoder
to produce a string from byte[], NumericField uses this
ByteBuffer.wrap(byte[]).getXxx()-like stuff. FieldsReader can handle this.
I already proposed that in 2.9 but we got strong -1 from some committers. This
would make the API clean. I would propose that for 4.0 (maybe when we get
codecs for stored fields).
> 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
