[
https://issues.apache.org/jira/browse/LUCENE-4591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511319#comment-13511319
]
Adrien Grand commented on LUCENE-4591:
--------------------------------------
Hi Renaud,
My concern about a per-field StoredFieldsFormat is that it would increase the
number of disk seeks required to load all the stored fields of a document (the
current default StoredFieldsFormat impl requires only one disk seek to load all
the fields of a document). What are you willing to optimize with a per-field
StoredFieldsFormat?
> Make StoredFieldsFormat more configurable
> -----------------------------------------
>
> Key: LUCENE-4591
> URL: https://issues.apache.org/jira/browse/LUCENE-4591
> 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 PostingsFormat.
> 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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
