t version of the solr
> doesn't seem to like control characters
>> (\005, in this case), but previous
> versions handled them (or at least
>> ignored them).
>>
>> These characters
> shouldn't be in my documents, so there's a bug on my
>> end to track do
se characters shouldn't be in my documents, so there's a bug on my
>> end to track down. However, I'm wondering if this was an expected
>> change or an unintended consequence of recent work . . .
>>
>>
>>
>>
>> --
>> ---
(or at least
> ignored them).
>
> These characters shouldn't be in my documents, so there's a bug on my
> end to track down. However, I'm wondering if this was an expected
> change or an unintended consequence of recent work . . .
>
>
>
>
> --
> ---------------------
From the XML 1.0 spec.: "Legal characters are tab, carriage return,
line feed, and the legal graphic characters of Unicode and ISO/IEC
10646." So, \005 is not a legal XML character. It appears the old StAX
implementation was more lenient than it should have been and Woodstox is
doing the corr
My guess is it has to do with switching the StAX implementation to
geronimo API and the woodstox implementation
https://issues.apache.org/jira/browse/SOLR-770
I'm not sure what the solution is though...
On Sep 17, 2008, at 10:02 PM, Joshua Reedy wrote:
I have been using a stable dev versio
I have been using a stable dev version of 1.3 for a few months.
Today, I began testing the final release version, and I encountered a
strange problem.
The only thing that has changed in my setup is the solr code (I didn't
make any config change or change the schema).
a document has a text field wi
