[
https://issues.apache.org/jira/browse/SOLR-12330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759168#comment-16759168
]
Cesar Rodriguez commented on SOLR-12330:
----------------------------------------
[~mkhludnev], in regard to the following:
{quote}I suppose we can't hunt for those NPE rows one by one, but rater wrap
FacetModule invocation with catch(Exception e) {throw new
SolrException(...,e);}{quote}
I believe you are already aware, but in case it helps, among the 28 issues we
have already submitted this week, 6 of them seem to be related to the facet
module:
https://issues.apache.org/jira/browse/SOLR-13206?jql=labels%20%3D%20diffblue%20AND%20text%20~%20%22facet%22
And 3 of them are NPEs. Each of those tickets contains a stack trace.
Would it be useful if we run a more detailed analysis in this module, aiming at
finding more NPEs or other issues? Cf. my mail to the developer's mailing list
last Monday.
> Referencing non existing parameter in JSON Facet "filter" (and/or other NPEs)
> either reported too little and even might be ignored
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-12330
> URL: https://issues.apache.org/jira/browse/SOLR-12330
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Facet Module
> Affects Versions: 7.3
> Reporter: Mikhail Khludnev
> Assignee: Mikhail Khludnev
> Priority: Major
> Attachments: SOLR-12330.patch, SOLR-12330.patch, SOLR-12330.patch
>
>
> Just encounter such weird behaviour, will recheck and followup.
> {{"filter":["\{!v=$bogus}"]}} responds back with just NPE which makes
> impossible to guess the reason.
> It might be even worse, since {{"filter":[\{"param":"bogus"}]}} seems like
> just silently ignored.
> Once agin, I'll double check.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
