A big thanks to Yonik and Mark. Using the raw term query I was able
to find the range(!) of documents that had bad integer field values.
Deleting those documents, committing and optimizing cleared up the
issue.
Still not sure how the bad values were inserted in the first place,
but that is anothe
On Fri, Feb 26, 2010 at 10:59 AM, Mark Miller wrote:
> You have to find the document with the bad value somehow.
>
> In the past I have used Luke to help with this.
>
> Then you need to delete the document.
You can also find the document with a raw term query.
q={!raw f=myfield}104708<
-Yonik
h
eturn 0 results, but still has a sort
parameter the exception is raised. The stack trace is the same no
matter what the query.
I need help troubleshooting this issue. Any clues, or suggested
approaches would be helpful. Thank you in advance!.
The stack trace is as follows:
SEVERE: java.la
but still has a sort
>> parameter the exception is raised. The stack trace is the same no
>> matter what the query.
>>
>> I need help troubleshooting this issue. Any clues, or suggested
>> approaches would be helpful. Thank you in advance!.
>>
&
till has a sort
> parameter the exception is raised. The stack trace is the same no
> matter what the query.
>
> I need help troubleshooting this issue. Any clues, or suggested
> approaches would be helpful. Thank you in advance!.
>
> The stack trace is as fol
: java.lang.NumberFormatException: For input string: "104708<"
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:456)
at java.lang.Integer.parseInt(Integer.java:49
