[
https://issues.apache.org/jira/browse/SOLR-12330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16754594#comment-16754594
]
Munendra S N commented on SOLR-12330:
-------------------------------------
Also, there are other cases where referencing non-exist parameter will give NPE
with status 500. One such case which I encountered is in function query
SOLR-11883. I suspect there are other cases also where same issue occurs.
Should the cases be handled differently or should be handled in *parse* method
so that all the cases are covered?
> 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]
