[
https://issues.apache.org/jira/browse/LUCENE-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114024#comment-13114024
]
Robert Muir commented on LUCENE-2621:
-------------------------------------
I think so, assuming FieldInfos etc are *also* read/written by the codec.
Then I think PFCW could be an abstract class that writes per-field
configuration into the index, but for example PreFlexCodec would *not* extend
this class, as a 3.x index is the same codec across all fields.
I think if we do things this way we have a lot more flexibility with backwards
compatibility instead of all this if-then-else conditional version-checking
code when reading these files...
Really, for example if someone wanted to make a Codec that reads a lucene 2.x
indexes (compressed fields and all) they should be able to do this if we
reorganize this right.
> Extend Codec to handle also stored fields and term vectors
> ----------------------------------------------------------
>
> Key: LUCENE-2621
> URL: https://issues.apache.org/jira/browse/LUCENE-2621
> Project: Lucene - Java
> Issue Type: Improvement
> Components: core/index
> Affects Versions: 4.0
> Reporter: Andrzej Bialecki
> Assignee: Robert Muir
> Labels: gsoc2011, lucene-gsoc-11, mentor
> Attachments: LUCENE-2621_rote.patch
>
>
> Currently Codec API handles only writing/reading of term-related data, while
> stored fields data and term frequency vector data writing/reading is handled
> elsewhere.
> I propose to extend the Codec API to handle this data as well.
--
This message is automatically generated by JIRA.
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
