Ian: I don't know enough about the BinaryResponseWriter or shard searching
to really know what the root cause of the problen is here, but it sound
like a bug that should be fixed ... could you pelase file one in Jira and
mark it "Fix Version: 1.3" (we should figure it out before 1.3 goes out)
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) {
More of an update and work around. 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.
Should I open a bug for this?
On Thu, Aug 21, 2008 at 8:56 AM, Ian Connor <[EMAIL PROTECTED]> wrote:
> I think I have
I think I have narrowed it down to:
where integer is defined in the example as:
It returns fine when I query directly, but blows up when going through
the binary conversion that shards uses.
On Thu, Aug 21, 2008 at 8:37 AM, Ian Connor <[EMAIL PROTECTED]> wrote:
> Hi,
>
> What is the b
Hi,
What is the best way to figure out which field is giving this error:
Aug 21, 2008 8:34:17 AM org.apache.solr.common.SolrException log
SEVERE: java.lang.NumberFormatException: For input string: ""
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
