[
https://issues.apache.org/jira/browse/SOLR-12330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763382#comment-16763382
]
Munendra S N commented on SOLR-12330:
-------------------------------------
[~mkhludnev]
I missed some previous updates on this issue. I agree with you that ambiguous
references should be handled and it should have and dedicated issue as impact
wise its big change.
In the latest patch, you have dropped documentation related changes. Is that
expected or a miss?
One request, could you please change the contributor line in *Changes.txt* to
include you as co-contributor *Munendra S N, Mikhail Khludnev*(I'm not sure if
this the convention for co-contributing). I worked on the basic patch provided
by you So, I consider your contribution is equal to mine if not more
> JSON Facet syntax errors are responded as runtime exceptions with 500 code
> --------------------------------------------------------------------------
>
> 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-combined.patch, SOLR-12330.patch,
> SOLR-12330.patch, SOLR-12330.patch, SOLR-12330.patch, SOLR-12330.patch,
> SOLR-12330.patch, 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. Turns out it's ok see SOLR-9682
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
