[
https://issues.apache.org/jira/browse/LUCENE-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-5090:
---------------------------------------
Attachment: LUCENE-5090.patch
Initial patch w/ test case & fix ... I'm a little uncertain about the logic I
did to "crawl up" to the original parent reader ... do we already have a
utility method somewhere to do this?
> 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: [email protected]
For additional commands, e-mail: [email protected]
