[
https://issues.apache.org/jira/browse/SOLR-7765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-7765.
----------------------------
Resolution: Fixed
Fix Version/s: Trunk
5.3
Thanks for rasiing this issue and helping out with the tests Konstantin,
bq. Is there any reason to use reversed order in ifs...
It's just a defensive coding habbit i developed from doing a lot of C and perl
coding in my early years as a developer ... trained my brain to default to
putting constants on the left in comparisons in cause i misstype "=" instead of
"==" or "<="
> TokenizerChain methods may return null depending on how constructor is called
> -- causes NPE in luke request handler
> -------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-7765
> URL: https://issues.apache.org/jira/browse/SOLR-7765
> Project: Solr
> Issue Type: Bug
> Affects Versions: 5.2.1
> Reporter: Konstantin Gribov
> Assignee: Hoss Man
> Priority: Minor
> Fix For: 5.3, Trunk
>
> Attachments: SOLR-7765.patch, SOLR-7765.patch, SOLR-7765.patch
>
>
> {{TokenizerChain}} created using 2-arg constructor has {{null}} in
> {{charFilters}}, so {{LukeRequestHandler}} throws NPE on iterating it.
> {{TokenizerChain}} constructor's should be hardened to do explicit null
> checks, throwing early NPE where appropriate (tokenizer factory), or
> initializing internal arrays to have 0 length when optional (factories for
> char filters and token filters)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
