lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Wang (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4569) Allow customization of column stride field and norms via indexing chain
Date Wed, 28 Nov 2012 18:02:58 GMT


John Wang commented on LUCENE-4569:

Thanks Simon! No rush, was just wanted some feedback. 

Do you think we should do the same for stored fields?

Chris: we are building a custom IndexingChain which is at a higher level than Codecs. You
are definitely right, and currently I am able to get what I needed via a codec. e.g. our custom
indexing chain to handle indexed documents, and then register a codec to intercept the code
path for norms and CSF, but this ends up with 2 customization hooks for the same indexer.


> Allow customization of column stride field and norms via indexing chain
> -----------------------------------------------------------------------
>                 Key: LUCENE-4569
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/index
>    Affects Versions: 4.0
>            Reporter: John Wang
>            Assignee: Simon Willnauer
>         Attachments: patch.diff
> We are building an in-memory indexing format and managing our own segments. We are doing
this by implementing a custom IndexingChain. We would like to support column-stride-fields
and norms without having to wire in a codec (since we are managing our postings differently)
> Suggested change is consistent with the api support for passing in a custom InvertedDocConsumer.

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