[
https://issues.apache.org/jira/browse/LUCENE-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-4971:
---------------------------------------
Attachment: LUCENE-4971.patch
Patch with a test case showing the NPE.
The question is how to fix it ... SpecialOperations.getFiniteStrings today
returns null when it hits the limit, yet, it has accumulated the first N
strings it saw at that point, so maybe we should change it to return the first
N so that we have something to build?
Or alternatively, AnalyzingSuggester could just skip a given input if it
created too many strings.
> NPE in AnalyzingSuggester
> -------------------------
>
> Key: LUCENE-4971
> URL: https://issues.apache.org/jira/browse/LUCENE-4971
> Project: Lucene - Core
> Issue Type: Bug
> Affects Versions: 4.1
> Environment: Windows 7
> Reporter: Alexey Kudinov
> Assignee: Michael McCandless
> Fix For: 5.0, 4.4
>
> Attachments: LUCENE-4971.patch
>
>
> Setting maxGraphExpansions > 0 with a lot of expansions (e.g. due to
> synonyms).
> Set<IntsRef> paths = toFiniteStrings(surfaceForm, ts2a);
> paths may be null, so maxAnalyzedPathsForOneInput =
> Math.max(maxAnalyzedPathsForOneInput, paths.size()) may end with NPE
--
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]
