[jira] [Commented] (LUCENE-4569) Allow customization of column stride field and norms via indexing chain
[ https://issues.apache.org/jira/browse/LUCENE-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13673539#comment-13673539 ] John Wang commented on LUCENE-4569: --- Hi Simon: Looked at the latest code on trunk, it seems that I can just add my own DocValuesConsumer on line 94 in DWPT. Do you think that is the right way of doing this? I will resolve this issue since seems that the trunk code is suppor what I need. -John Allow customization of column stride field and norms via indexing chain --- Key: LUCENE-4569 URL: https://issues.apache.org/jira/browse/LUCENE-4569 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: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4569) Allow customization of column stride field and norms via indexing chain
[ https://issues.apache.org/jira/browse/LUCENE-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13671501#comment-13671501 ] Simon Willnauer commented on LUCENE-4569: - John, I looked at the current code and it seems that everything delegates do segmentsInfo.codec and I wonder if you can't just use a FilteredCodec for this and extend it in DWPT? Allow customization of column stride field and norms via indexing chain --- Key: LUCENE-4569 URL: https://issues.apache.org/jira/browse/LUCENE-4569 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: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4569) Allow customization of column stride field and norms via indexing chain
[ https://issues.apache.org/jira/browse/LUCENE-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13671164#comment-13671164 ] John Wang commented on LUCENE-4569: --- Hey Simon: Was wondering if you had a chance to look at this. Thanks -John Allow customization of column stride field and norms via indexing chain --- Key: LUCENE-4569 URL: https://issues.apache.org/jira/browse/LUCENE-4569 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: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4569) Allow customization of column stride field and norms via indexing chain
[ https://issues.apache.org/jira/browse/LUCENE-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505294#comment-13505294 ] Chris Male commented on LUCENE-4569: John, I don't really know much about the API you're wanting to change, but to help me understand are you able to explain more what you're trying to do in your custom indexing format / code? I think one of the major motivation for Codecs is to allow this sort of customization through their API (there is already Codecs for holding this in memory). Allow customization of column stride field and norms via indexing chain --- Key: LUCENE-4569 URL: https://issues.apache.org/jira/browse/LUCENE-4569 Project: Lucene - Core Issue Type: Improvement Components: core/index Affects Versions: 4.0 Reporter: John Wang 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: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4569) Allow customization of column stride field and norms via indexing chain
[ https://issues.apache.org/jira/browse/LUCENE-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505658#comment-13505658 ] Simon Willnauer commented on LUCENE-4569: - sorry john, busy times over here... I will look into that later this week though. seems pretty straight forward to me at a first glance ie. doesn't hurt anyone Allow customization of column stride field and norms via indexing chain --- Key: LUCENE-4569 URL: https://issues.apache.org/jira/browse/LUCENE-4569 Project: Lucene - Core Issue Type: Improvement Components: core/index Affects Versions: 4.0 Reporter: John Wang 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: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-4569) Allow customization of column stride field and norms via indexing chain
[ https://issues.apache.org/jira/browse/LUCENE-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505718#comment-13505718 ] 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. Thanks! -John Allow customization of column stride field and norms via indexing chain --- Key: LUCENE-4569 URL: https://issues.apache.org/jira/browse/LUCENE-4569 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: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
