[
https://issues.apache.org/jira/browse/SOLR-840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648089#action_12648089
]
Shalin Shekhar Mangar commented on SOLR-840:
--------------------------------------------
Ian, is it possible that you changed the schema from a string to integer/sint
and did not re-index? I'm not sure why an empty string will be there in an
integer field. Anyway, we should handle this kind of error.
> 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
>
> Attachments: SOLR-840.patch
>
> 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.
