yho On Sunday, October 6, 2013, Shai Erera (JIRA) wrote:u
> > [ > https://issues.apache.org/jira/browse/LUCENE-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787730#comment-13787730] > > Shai Erera commented on LUCENE-5189: > ------------------------------------ > > bq. If SR itself doesnt need ref-counting, perhaps we can pull this out of > SR then? (rote-refactor into DV-thingy or something). > > You mean something like SegmentDocValues? It's doable I guess. SR would > need to keep track of the DV.gens it uses though, so that in SR.doClose it > can call segDV.decRef(gens) so that the latter can decRef all the DVPs that > are used for these gens. If it also removes a gen from the map when it's no > longer referenced by any SR, we don't need to take care of clearing the > genDVP map when all SRs were closed (otherwise I think we'll need to > refCount SegDV too, like SCR). > > I'll give it a shot. > > > 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-4x.patch, LUCENE-5189.patch, > LUCENE-5189.patch, LUCENE-5189.patch, LUCENE-5189.patch, LUCENE-5189.patch, > LUCENE-5189.patch, LUCENE-5189.patch, LUCENE-5189.patch, LUCENE-5189.patch, > LUCENE-5189.patch, LUCENE-5189.patch, LUCENE-5189_process_events.patch, > LUCENE-5189_process_events.patch, LUCENE-5189-updates-order.patch, > LUCENE-5189-updates-order.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 was sent by Atlassian JIRA > (v6.1#6144) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] <javascript:;> > For additional commands, e-mail: [email protected] <javascript:;> > >
