lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Renaud Delbru (JIRA)" <>
Subject [jira] [Comment Edited] (LUCENE-4055) Refactor SegmentInfo / FieldInfo to make them extensible
Date Sun, 27 May 2012 13:46:23 GMT


Renaud Delbru edited comment on LUCENE-4055 at 5/27/12 1:44 PM:

Does this patch allows TermsHashConsumerPerField to be dependent to the Codec/Field ? I have
a use case where I need my own TermsHashConsumerPerField for certain fields.

At the moment, the only extension of TermsHashConsumer is FreqProxTermsWriter which is creating
a FreqProxTermsWriterPerField for every field (see FreqProxTermsWriter#addField()).

A possible solution of my problem would be to have a PostingsTermsWriter (extension of TermsHashConsumer)
that will create a specific PostingsTermsWriterPerField (extension of TermsHashConsumerPerField)
depending on the codec information found in the FieldInfo object.
      was (Author: renaud.delbru):
    Does this patch allows FreqProxTermsWriterPerField to be dependent to the Codec/Field
? I have a use case where I need my own FreqProxTermsWriterPerField for certain fields.

I am asking this because I see in your patch the following line in

final FreqProxTermsWriterPerField fieldWriter = allFields.get(fieldNumber);

which seems to retrieve a particular FreqProxTermsWriterPerField for each field type.
> Refactor SegmentInfo / FieldInfo to make them extensible
> --------------------------------------------------------
>                 Key: LUCENE-4055
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: core/codecs
>            Reporter: Andrzej Bialecki 
>            Assignee: Robert Muir
>             Fix For: 4.0
>         Attachments: LUCENE-4055.patch
> After LUCENE-4050 is done the resulting SegmentInfo / FieldInfo classes should be made
abstract so that they can be extended by Codec-s.

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


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

View raw message