[
https://issues.apache.org/jira/browse/LUCENE-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-3453:
---------------------------------------
Attachment: LUCENE-3453.patch
Applyable patch; I still need to go through it more closely but I
think it's basically ready. I'd like to commit it soon... it's a big
patch so it's going to quickly get stale/conflict. We can further
iterate on trunk...
I ended up keeping (but simplifying) DocValuesField, as sugar, and
making a number of other simplifications:
* Removed custom Comparator from DocValuesField, meaning sort is
always by unsigned byte (UTF8/unicode) order now.
* Moved numeric field type information out of IndexableField into
FieldType.
* LUCENE-3682: added in "transition layer" to construct Field using
the pre-4.0 enums (Store, Index, TermVector)
* LUCENE-3694: moved all setXXX methods in NumericField and
DocValuesField up into Field.java (as setValue methods)
* Renamed/generalized BinaryField to StoredField, so that you can
use it to store any value, including numerics. I generalized the
codecs so they mark a stored field as numeric if its
.numericValue() is non-null, and at document load time they now
always create a StoredField instance. This also means you have to
call .numericValue (not .stringValue()) on the returned
StoredField, after indexing a NumericField.
* LUCENE-3616: fail if you try to create a TokenStream field that's
stored.
* Added numerics to Field ctor/setValue/numericValue; this is used
by DocValuesField, NumericField, StoredField
* You can still reuse a Field (change its value), however I madte
this more strict: you can only change the value to another value
of the same type.
> remove IndexDocValuesField
> --------------------------
>
> Key: LUCENE-3453
> URL: https://issues.apache.org/jira/browse/LUCENE-3453
> Project: Lucene - Java
> Issue Type: Bug
> Affects Versions: 4.0
> Reporter: Robert Muir
> Assignee: Michael McCandless
> Fix For: 4.0
>
> Attachments: LUCENE-3453.patch, LUCENE-3453.patch
>
>
> Its confusing how we present CSF functionality to the user, its actually not
> a "field" but an "attribute" of a field like STORED or INDEXED.
> Otherwise, its really hard to think about CSF because there is a mismatch
> between the APIs and the index format.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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]
