[
https://issues.apache.org/jira/browse/LUCENE-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16857003#comment-16857003
]
Andrzej Bialecki commented on LUCENE-8832:
-------------------------------------------
Sure. Currently I'm exploring ways to define and record the mappings as
userData in a SegmentCommitInfo, and have the Codec use this information for
re-mapping. Once this part is in place for all intents and purposes the
segments will appear as if the fields were already renamed / deleted, so the
forced singleton merges with do The Right Thing.
> Support for field removal and renaming
> --------------------------------------
>
> Key: LUCENE-8832
> URL: https://issues.apache.org/jira/browse/LUCENE-8832
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Major
>
> Currently it's not possible to rename existing Lucene fields or delete them
> without creating a new index from scratch (FieldInfos are basically
> append-only).
> This issue proposes to investigate an approach that applies these changes at
> a Codec level so that the unwanted data is skipped over (in case of field
> delete) or accessed under a different name (in case of field rename). Since
> the same Codec API is used for segment merging the deletion / removal
> filtering could be applied only to the currently existing segments because
> the resulting merged segments would not contain this data anymore.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
