You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2014/08/20 07:56:18 UTC
[jira] [Updated] (LUCENE-5894) refactor bulk merge logic
[ https://issues.apache.org/jira/browse/LUCENE-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Muir updated LUCENE-5894:
--------------------------------
Attachment: LUCENE-5894.patch
Stab at a patch:
* moved all bulk merge stuff out of segmentmerger to codec private
* moved all merge logic out of segment merger into codec apis (so they can completely override)
* added missing getXXXReader to SegmentReader, its not needed for postings as we already have direct access with fields(), but is needed for norms/docvalues
* separated norms processing from docvalues
* refactored dv update handling: when dv updates are in place you get a producer that delegates to the correct ones (this is a nice separation out of SR)
> refactor bulk merge logic
> -------------------------
>
> Key: LUCENE-5894
> URL: https://issues.apache.org/jira/browse/LUCENE-5894
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Robert Muir
> Attachments: LUCENE-5894.patch
>
>
> Today its only usable really by stored fields/term vectors, has hardcoded logic in SegmentMerger specific to certain impls, etc.
> It would be better if this was generalized to terms/postings/norms/docvalues as well.
> Bulk merge is boring, the real idea is to allow codecs to do more: e.g. with this patch they could do streaming checksum validation, or prevent the loading of "latent" norms, or other things we cannot do today.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org