[
https://issues.apache.org/jira/browse/SOLR-840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646292#action_12646292
]
ian connor commented on SOLR-840:
---------------------------------
HTTP ERROR: 500
parsing error
org.apache.solr.common.SolrException: parsing error
at
org.apache.solr.client.solrj.impl.BinaryResponseParser.processResponse(BinaryResponseParser.java:41)
at
org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:385)
at
org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:183)
at
org.apache.solr.handler.component.HttpCommComponent$1.call(SearchHandler.java:396)
at
org.apache.solr.handler.component.HttpCommComponent$1.call(SearchHandler.java:369)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:675)
Caused by: java.io.EOFException
at
org.apache.solr.common.util.FastInputStream.readByte(FastInputStream.java:160)
at
org.apache.solr.common.util.NamedListCodec.readVal(NamedListCodec.java:143)
at
org.apache.solr.common.util.NamedListCodec.readArray(NamedListCodec.java:367)
at
org.apache.solr.common.util.NamedListCodec.readVal(NamedListCodec.java:153)
at
org.apache.solr.common.util.NamedListCodec.readSolrDocumentList(NamedListCodec.java:301)
at
org.apache.solr.common.util.NamedListCodec.readVal(NamedListCodec.java:172)
at
org.apache.solr.common.util.NamedListCodec.readOrderedMap(NamedListCodec.java:98)
at
org.apache.solr.common.util.NamedListCodec.readVal(NamedListCodec.java:154)
at
org.apache.solr.common.util.NamedListCodec.unmarshal(NamedListCodec.java:89)
at
org.apache.solr.client.solrj.impl.BinaryResponseParser.processResponse(BinaryResponseParser.java:39)
... 12 more
RequestURI=/solr/select/
> BinaryResponseWriter does not handle nulls with shards as it does locally
> -------------------------------------------------------------------------
>
> Key: SOLR-840
> URL: https://issues.apache.org/jira/browse/SOLR-840
> Project: Solr
> Issue Type: Bug
> Components: search
> Affects Versions: 1.3
> Environment: All
> Reporter: ian connor
> Fix For: 1.3.1
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> When you query a number field
> locally, it can return null. However, when you go through a shard if
> you have an empty number it throws an error.
> I found wrapping the BinaryResponseWrite with a try/catch solved the
> problem and allows null values to be returned.
> BinaryResponseWriter.java:141
> try {
> val = useFieldObjects ? ft.toObject(f) : ft.toExternal(f);
> } catch (NumberFormatException e) {
> val = null;
> }
> It seems only the BinaryResponseWriter is actually that fussy about
> null items. Once it comes back to the client for display, it is
> handled without error.
> Hoss suggested this should be fixed for 1.3 but now that it has shipped I
> have marked it as 1.3.1 (
> See:
> http://www.nabble.com/best-way-to-debug-shard-format-errors-td19087854.html)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
