lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Renaud Delbru (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4591) Make StoredFieldsFormat more configurable
Date Thu, 06 Dec 2012 14:39:09 GMT


Renaud Delbru commented on LUCENE-4591:

How would you do that? As far as I know, the only way to access stored fields is through the
StoredFieldVisitor API

Yes, but we can pass our own implementation of StoredFieldVisitor with our own specific information
about what to retrieve.

So from Adrien and Robert feedback, it looks like you do not really want to see a perfield
StoredFieldsFormat mechanism. that's fine and understandable. 
Could we instead try to open/extend the current code base so that we are more free to extend
it on our side ? For example, opening CompressingStoredFieldsWriter and CompressingStoredFieldsReader,
as well as making them configurable with a segment suffixes ? That would greatly help.
> Make StoredFieldsFormat more configurable
> -----------------------------------------
>                 Key: LUCENE-4591
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/codecs
>    Affects Versions: 4.1
>            Reporter: Renaud Delbru
>             Fix For: 4.1
> The current StoredFieldsFormat are implemented with the assumption that only one type
of StoredfieldsFormat is used by the index.
> We would like to be able to configure a StoredFieldsFormat per field, similarly to the
> There is a few issues that need to be solved for allowing that:
> 1) allowing to configure a segment suffix to the StoredFieldsFormat
> 2) implement SPI interface in StoredFieldsFormat 
> 3) create a PerFieldStoredFieldsFormat
> We are proposing to start first with 1) by modifying the signature of StoredFieldsFormat#fieldsReader
and StoredFieldsFormat#fieldsWriter so that they use SegmentReadState and SegmentWriteState
instead of the current set of parameters.
> Let us know what you think about this idea. If this is of interest, we can contribute
with a first path for 1).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message