[
https://issues.apache.org/jira/browse/LUCENE-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791056#action_12791056
]
Michael McCandless commented on LUCENE-2160:
--------------------------------------------
bq. Looked at the file format wiki more closely, I see front-coding applies to
all the terms in all fields. So my above comment would not work.
Yeah I think you'll be in trouble in general if your new name doesn't "fit" in
the same sort; you could check and allow a rename as long as it doesn't change
the sort order?
bq. Do you think it makes sense to have a tii,tis file for each indexed field?
Would the new codec allow for it?
A new codec would definitely be free to store however it wanted...
But even the standard codec (default codec for flex, most similar to the
current index format) actually shouldn't mind if the fields are not in sorted
order (though I haven't tested this!). It separately stores the seek position
of each field... though we may need to fix the FieldsEnum to do the sorting if
the index is no longer sorted.
> Tool to rename a field
> ----------------------
>
> Key: LUCENE-2160
> URL: https://issues.apache.org/jira/browse/LUCENE-2160
> Project: Lucene - Java
> Issue Type: New Feature
> Components: contrib/*
> Affects Versions: 3.0
> Reporter: John Wang
> Attachments: RenameField.java, RenameField.java
>
>
> We found it useful to be able to rename a field.
> It can save a lot of reindexing time/cost when being used in conjunction with
> ParallelReader to update partially a field.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
