[
https://issues.apache.org/jira/browse/LUCENE-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758311#comment-13758311
]
Shai Erera commented on LUCENE-5189:
------------------------------------
I think global FIS is an interesting idea, but per-segment FIS.gen is a lower
hanging fruit. I did it once and it was quite straightforward (maybe someone
will have reservations on how I did it though):
* SIS tracks fieldInfosGen (in this patch, rename all dvGen in SIS to fisGen)
* FI tracks dvGen
* A new FIS45Format reads/writes each FI's dvGen
* ReaderAndLiveDocs writes a new FIS gen, containing the entire FIS, so SR only
reads the latest gen to load FIS
I think we should explore global FIS separately, because it brings its own
issues, e.g. do we keep FISFormat or nuke it? Who invokes it (probably SIS)?
It's also quite orthogonal to that issue, or at least, we can proceed with it
and improve FIS gen'ing later with global FIS.
As for SI.attributes(), I think we can move them under SIS. We should open an
issue to do that.
> 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
