[
https://issues.apache.org/jira/browse/LUCENE-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757885#comment-13757885
]
Robert Muir commented on LUCENE-5189:
-------------------------------------
{quote}
Just so I understand, if we gen FieldInfos, does that solve the brokenness of
the Codec APIs (in addition to the other things that it solves)? If not, in
what way are they broken, and is this break a new thing that NDV updates
cause/expose, or it's a break that exists in general? Can you list the breaks
here (because I think that FIS.gen solves all the points you raised above).
{quote}
It does not solve problem #2 (SegmentInfos.attributes). This API should
removed, deprecated, made internal-only, or something like that. Another option
is to move this stuff into the commit, but that might be overkill: today this
stuff is only used as a backwards-compatibility crutch (i think) to read 3.x
indexes: so it can possibly be just removed in trunk right now.
Gen'ing FieldInfos brings about its own set of questions as far as when/how/if
any new fieldinfo information is merged and when/how its visible to the codec
API. its very scary but I don't see any alternative at the moment.
> Numeric DocValues Updates
> -------------------------
>
> Key: LUCENE-5189
> URL: https://issues.apache.org/jira/browse/LUCENE-5189
> Project: Lucene - Core
> Issue Type: New Feature
> Components: core/index
> Reporter: Shai Erera
> Assignee: Shai Erera
> Attachments: LUCENE-5189.patch, LUCENE-5189.patch, LUCENE-5189.patch,
> LUCENE-5189.patch, LUCENE-5189.patch, LUCENE-5189.patch, LUCENE-5189.patch
>
>
> In LUCENE-4258 we started to work on incremental field updates, however the
> amount of changes are immense and hard to follow/consume. The reason is that
> we targeted postings, stored fields, DV etc., all from the get go.
> I'd like to start afresh here, with numeric-dv-field updates only. There are
> a couple of reasons to that:
> * NumericDV fields should be easier to update, if e.g. we write all the
> values of all the documents in a segment for the updated field (similar to
> how livedocs work, and previously norms).
> * It's a fairly contained issue, attempting to handle just one data type to
> update, yet requires many changes to core code which will also be useful for
> updating other data types.
> * It has value in and on itself, and we don't need to allow updating all the
> data types in Lucene at once ... we can do that gradually.
> I have some working patch already which I'll upload next, explaining the
> changes.
--
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
