[
https://issues.apache.org/jira/browse/SOLR-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tanguy Moal updated SOLR-3783:
------------------------------
Description:
We get an http 500 as follow :
{code:xml}
<lst name="error">
<str name="trace">java.lang.NullPointerException</str>
<int name="code">500</int>
</lst>
{code}
When facet.missing is turned on and combined with facet.pivot (if one of the
pivot-faceted fields have missing counts ^-^)
Ideally, the decission tree could be computing for the missing "entries" using
the {noformat} -field:[* TO *] {noformat} query but it might be a performance
issue on a large index (I guess)
The fallback to this could be to raise a 400 error with a clean message telling
that both parameters can't be combined and then the documentation should be
modified accordingly.
was:
We get an http 500 as follow :
{code:xml}
<lst name="error">
<str name="trace">java.lang.NullPointerException</str>
<int name="code">500</int>
</lst>
{code}
When facet.missing is turned on and combined with facet.pivot (if one of the
pivot-faceted fields have missing counts ^-^)
Ideally, the decission tree could be computing for the missing "entries" using
the -field:[* TO *] query but it might be a performance issue on a large index
(I guess)
The fallback to this could be to raise a 400 error with a clean message telling
that both parameters can't be combined and then the documentation should be
modified accordingly.
> Facet pivots produces NPE when facet.missing is turned on
> ---------------------------------------------------------
>
> Key: SOLR-3783
> URL: https://issues.apache.org/jira/browse/SOLR-3783
> Project: Solr
> Issue Type: Bug
> Components: SearchComponents - other
> Reporter: Tanguy Moal
> Priority: Minor
>
> We get an http 500 as follow :
> {code:xml}
> <lst name="error">
> <str name="trace">java.lang.NullPointerException</str>
> <int name="code">500</int>
> </lst>
> {code}
> When facet.missing is turned on and combined with facet.pivot (if one of the
> pivot-faceted fields have missing counts ^-^)
> Ideally, the decission tree could be computing for the missing "entries"
> using the {noformat} -field:[* TO *] {noformat} query but it might be a
> performance issue on a large index (I guess)
> The fallback to this could be to raise a 400 error with a clean message
> telling that both parameters can't be combined and then the documentation
> should be modified accordingly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
