[ 
https://issues.apache.org/jira/browse/LUCENE-8610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Gibney resolved LUCENE-8610.
------------------------------------
       Resolution: Not A Bug
    Lucene Fields:   (was: New,Patch Available)

Will look at addressing this in {{solr.PreAnalyzedAnalyzer}}. There may be 
other {{TokenStreams}} that don't strictly follow the requirement to initialize 
all token Attributes on instantiation, but as of now nothing relating to this 
issue is known to be broken.

> NPE in TermsHashPerField.add() for TokenStreams with lazily instantiated 
> token Attributes
> -----------------------------------------------------------------------------------------
>
>                 Key: LUCENE-8610
>                 URL: https://issues.apache.org/jira/browse/LUCENE-8610
>             Project: Lucene - Core
>          Issue Type: Wish
>          Components: core/index
>    Affects Versions: 7.4, master (8.0)
>            Reporter: Michael Gibney
>            Priority: Minor
>         Attachments: LUCENE-8610.patch
>
>
> {{DefaultIndexingChain.invert(...)}} callsĀ 
> {{invertState.setAttributeSource(stream)}} before {{stream.incrementToken()}} 
> is called.
> For instances of {{stream}} that lazily instantiate token attributes (e.g., 
> as {{solr.PreAnalyzedField$PreAnalyzedTokenizer}} does upon the first call to 
> {{incrementToken()}} that returns {{true}}), this can result in caching a 
> {{null}} value in {{invertState.termAttribute}} for a given {{stream}} 
> instance.
> Subsequent calls that reuse the same {{stream}} instance (reusing 
> {{TokenStreamComponents}}) for field values with at least 1 token will call 
> {{termHashPerField.start(...)}} which sets {{termsHashPerField.termAtt}} from 
> the {{null}} value cached in the {{FieldInvertState.termAttribute}}. An NPE 
> would be thrown when {{termsHashPerField.add()}} reasonably but incorrectly 
> assumes a non-null value for {{termAtt}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to