[
https://issues.apache.org/jira/browse/LUCENE-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2621:
--------------------------------
Attachment: LUCENE-2621_rote.patch
Here is a minimal 'rote refactor' for stored fields, there is a lot more to do
(e.g. filenames/extensions should come from codec, segmentmerger optimizations
(bulk merging) should not be in the API but customized by the codec, the codec
name (format) of fields should be recorded in the index, we should implement a
simpletext version and refactor/generalize, ...)
but more importantly, I think we need to restructure the class hierarchy: Codec
is a per-field thing currently but I think the name "Codec" should represent
the entire index...
maybe what is Codec now should be named FieldCodec? maybe the parts of
CodecProvider (e.g. segmentinfosreader, storedfields, etc) should be be moved
to this new Codec class? in this world maybe PreFlex codec for example returns
its hardcoded representation for every field since in 3.x this stuff is *not*
per field, and with more of the back compat code refactored down into PreFlex.
Would be good to come up with a nice class naming/hierarchy that represents
reality here.
> 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: [email protected]
For additional commands, e-mail: [email protected]
