[jira] [Commented] (LUCENE-5090) SSDVA should detect a mismatch in the SSDVReaderState
[ https://issues.apache.org/jira/browse/LUCENE-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13708619#comment-13708619 ] ASF subversion and git services commented on LUCENE-5090: - Commit 1503327 from [~mikemccand] in branch 'dev/trunk' [ https://svn.apache.org/r1503327 ] LUCENE-5090: catch mismatched readers in SortedSetDocValuesAccumulator/ReaderState SSDVA should detect a mismatch in the SSDVReaderState - Key: LUCENE-5090 URL: https://issues.apache.org/jira/browse/LUCENE-5090 Project: Lucene - Core Issue Type: Improvement Components: modules/facet Reporter: Michael McCandless Assignee: Michael McCandless Fix For: 5.0, 4.4 Attachments: LUCENE-5090.patch, LUCENE-5090.patch This is trappy today: every time you open a new reader, you must create a new SSDVReaderState (this computes the seg - global ord mapping), and pass that to SSDVA. But if this gets messed up (e.g. you pass an old SSDVReaderState) it will result in confusing AIOOBE, or silently invalid results. -- 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-5090) SSDVA should detect a mismatch in the SSDVReaderState
[ https://issues.apache.org/jira/browse/LUCENE-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13708623#comment-13708623 ] ASF subversion and git services commented on LUCENE-5090: - Commit 1503329 from [~mikemccand] in branch 'dev/branches/branch_4x' [ https://svn.apache.org/r1503329 ] LUCENE-5090: catch mismatched readers in SortedSetDocValuesAccumulator/ReaderState SSDVA should detect a mismatch in the SSDVReaderState - Key: LUCENE-5090 URL: https://issues.apache.org/jira/browse/LUCENE-5090 Project: Lucene - Core Issue Type: Improvement Components: modules/facet Reporter: Michael McCandless Assignee: Michael McCandless Fix For: 5.0, 4.4 Attachments: LUCENE-5090.patch, LUCENE-5090.patch This is trappy today: every time you open a new reader, you must create a new SSDVReaderState (this computes the seg - global ord mapping), and pass that to SSDVA. But if this gets messed up (e.g. you pass an old SSDVReaderState) it will result in confusing AIOOBE, or silently invalid results. -- 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-5090) SSDVA should detect a mismatch in the SSDVReaderState
[ https://issues.apache.org/jira/browse/LUCENE-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13708626#comment-13708626 ] ASF subversion and git services commented on LUCENE-5090: - Commit 150 from [~mikemccand] in branch 'dev/branches/lucene_solr_4_4' [ https://svn.apache.org/r150 ] LUCENE-5090: catch mismatched readers in SortedSetDocValuesAccumulator/ReaderState SSDVA should detect a mismatch in the SSDVReaderState - Key: LUCENE-5090 URL: https://issues.apache.org/jira/browse/LUCENE-5090 Project: Lucene - Core Issue Type: Improvement Components: modules/facet Reporter: Michael McCandless Assignee: Michael McCandless Fix For: 5.0, 4.4 Attachments: LUCENE-5090.patch, LUCENE-5090.patch This is trappy today: every time you open a new reader, you must create a new SSDVReaderState (this computes the seg - global ord mapping), and pass that to SSDVA. But if this gets messed up (e.g. you pass an old SSDVReaderState) it will result in confusing AIOOBE, or silently invalid results. -- 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-5090) SSDVA should detect a mismatch in the SSDVReaderState
[ https://issues.apache.org/jira/browse/LUCENE-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13708823#comment-13708823 ] ASF subversion and git services commented on LUCENE-5090: - Commit 1503423 from [~mikemccand] in branch 'dev/trunk' [ https://svn.apache.org/r1503423 ] LUCENE-5090: fix test bug that was using mismatched readers when faceting with SortedSetDVs SSDVA should detect a mismatch in the SSDVReaderState - Key: LUCENE-5090 URL: https://issues.apache.org/jira/browse/LUCENE-5090 Project: Lucene - Core Issue Type: Improvement Components: modules/facet Reporter: Michael McCandless Assignee: Michael McCandless Fix For: 5.0, 4.4 Attachments: LUCENE-5090.patch, LUCENE-5090.patch This is trappy today: every time you open a new reader, you must create a new SSDVReaderState (this computes the seg - global ord mapping), and pass that to SSDVA. But if this gets messed up (e.g. you pass an old SSDVReaderState) it will result in confusing AIOOBE, or silently invalid results. -- 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-5090) SSDVA should detect a mismatch in the SSDVReaderState
[ https://issues.apache.org/jira/browse/LUCENE-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13708826#comment-13708826 ] ASF subversion and git services commented on LUCENE-5090: - Commit 1503424 from [~mikemccand] in branch 'dev/branches/branch_4x' [ https://svn.apache.org/r1503424 ] LUCENE-5090: fix test bug that was using mismatched readers when faceting with SortedSetDVs SSDVA should detect a mismatch in the SSDVReaderState - Key: LUCENE-5090 URL: https://issues.apache.org/jira/browse/LUCENE-5090 Project: Lucene - Core Issue Type: Improvement Components: modules/facet Reporter: Michael McCandless Assignee: Michael McCandless Fix For: 5.0, 4.4 Attachments: LUCENE-5090.patch, LUCENE-5090.patch This is trappy today: every time you open a new reader, you must create a new SSDVReaderState (this computes the seg - global ord mapping), and pass that to SSDVA. But if this gets messed up (e.g. you pass an old SSDVReaderState) it will result in confusing AIOOBE, or silently invalid results. -- 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-5090) SSDVA should detect a mismatch in the SSDVReaderState
[ https://issues.apache.org/jira/browse/LUCENE-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13708827#comment-13708827 ] ASF subversion and git services commented on LUCENE-5090: - Commit 1503425 from [~mikemccand] in branch 'dev/branches/lucene_solr_4_4' [ https://svn.apache.org/r1503425 ] LUCENE-5090: fix test bug that was using mismatched readers when faceting with SortedSetDVs SSDVA should detect a mismatch in the SSDVReaderState - Key: LUCENE-5090 URL: https://issues.apache.org/jira/browse/LUCENE-5090 Project: Lucene - Core Issue Type: Improvement Components: modules/facet Reporter: Michael McCandless Assignee: Michael McCandless Fix For: 5.0, 4.4 Attachments: LUCENE-5090.patch, LUCENE-5090.patch This is trappy today: every time you open a new reader, you must create a new SSDVReaderState (this computes the seg - global ord mapping), and pass that to SSDVA. But if this gets messed up (e.g. you pass an old SSDVReaderState) it will result in confusing AIOOBE, or silently invalid results. -- 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-5090) SSDVA should detect a mismatch in the SSDVReaderState
[
https://issues.apache.org/jira/browse/LUCENE-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13699423#comment-13699423
]
Robert Muir commented on LUCENE-5090:
-
ReaderUtil.getTopLevelContext ?
{code}
* Walks up the reader tree and return the given context's top level reader
* context, or in other words the reader tree's root context.
*/
public static IndexReaderContext getTopLevelContext(IndexReaderContext
context) {
while (context.parent != null) {
context = context.parent;
}
return context;
}
{code}
SSDVA should detect a mismatch in the SSDVReaderState
-
Key: LUCENE-5090
URL: https://issues.apache.org/jira/browse/LUCENE-5090
Project: Lucene - Core
Issue Type: Improvement
Components: modules/facet
Reporter: Michael McCandless
Assignee: Michael McCandless
Fix For: 5.0, 4.4
Attachments: LUCENE-5090.patch
This is trappy today: every time you open a new reader, you must create a new
SSDVReaderState (this computes the seg - global ord mapping), and pass that
to SSDVA.
But if this gets messed up (e.g. you pass an old SSDVReaderState) it will
result in confusing AIOOBE, or silently invalid results.
--
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-5090) SSDVA should detect a mismatch in the SSDVReaderState
[ https://issues.apache.org/jira/browse/LUCENE-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13699555#comment-13699555 ] Robert Muir commented on LUCENE-5090: - +1 SSDVA should detect a mismatch in the SSDVReaderState - Key: LUCENE-5090 URL: https://issues.apache.org/jira/browse/LUCENE-5090 Project: Lucene - Core Issue Type: Improvement Components: modules/facet Reporter: Michael McCandless Assignee: Michael McCandless Fix For: 5.0, 4.4 Attachments: LUCENE-5090.patch, LUCENE-5090.patch This is trappy today: every time you open a new reader, you must create a new SSDVReaderState (this computes the seg - global ord mapping), and pass that to SSDVA. But if this gets messed up (e.g. you pass an old SSDVReaderState) it will result in confusing AIOOBE, or silently invalid results. -- 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
