> Should I create a JIRA ticket?
already there:
https://issues.apache.org/jira/browse/SOLR-2005
we should provide a patch though ...
Regards,
Peter.
> With solrj doing a more like this query for a missing document:
> /mlt?q=docId:SomeMissingId
> always throws a null pointer exception:
> Caused by: org.apache.solr.client.solrj.SolrServerException: Error
> executing query
> at
> org.apache.solr.client.solrj.request.QueryRequest.process(QueryRequest.java:95)
>
> at
> org.apache.solr.client.solrj.SolrServer.query(SolrServer.java:118)
> at
> com.cmates.wopr.lucene.util.solr.RemoteSolrQueryService.lookup(RemoteSolrQueryService.java:91)
>
> ... 37 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.solr.client.solrj.response.QueryResponse.extractFacetInfo(QueryResponse.java:180)
>
> at
> org.apache.solr.client.solrj.response.QueryResponse.setResponse(QueryResponse.java:103)
>
> at
> org.apache.solr.client.solrj.response.QueryResponse.(QueryResponse.java:80)
>
> at
> org.apache.solr.client.solrj.request.QueryRequest.process(QueryRequest.java:89)
>
>
> What's happening is that the query coming back has
>
> perhaps the extractFacetInfo method should check that the passed in
> NamedList is null?
>
> This is causing me a problem as a SolrException is being thrown and
> this isn't really a solr issue ... it is an error on the person
> asking my service for a missing document id. I'll like to return a
> 400 error but can't accurately do that as a SolrException could mean
> something really went wrong on the solr server. So they get a 500
> error and it looks like from an operational standpoint that there's
> something really wrong.
>
> Thoughts? Should I create a JIRA ticket?
>
> Chris
>
--
http://jetwick.com twitter search prototype
