You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Marc Sturlese <ma...@gmail.com> on 2008/11/20 13:41:29 UTC
not string or text fields and shards
Hey there,
I have started working with an index divided in 3 shards. When I did a
distributed search I got an error with the fields that were not string or
text. I read that the error was due to BinaryResponseWriter and not
string/text empty fields.
I found the solution in an old thread of this forum:
http://www.nabble.com/best-way-to-debug-shard-format-errors-td19087854.html
The thing is I had to change some source code and rebuild solr. In that old
thread said that this problem would be solved in Solr 1.3. It is the version
that I am using but I still found the problem. Maybe there is a solution not
adding source that I couldn't know.
Does someone found any other solution?
Thanks in advance.
--
View this message in context: http://www.nabble.com/not-string-or-text-fields-and-shards-tp20600353p20600353.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: not string or text fields and shards
Posted by Ian Connor <ia...@gmail.com>.
That problem related to the score being computed when it was not in the
sort:
https://issues.apache.org/jira/browse/SOLR-626
To see if this is also your problem, you can make the score in the sort to
see if that stops the error. If you have the same issue, you can take the
patch and compile your own until it makes it into a stable build.
However, if you just have a bad field - this may not fix your problem and
your only choice is to clean up the data (think rebuild index).
On Sun, Nov 23, 2008 at 8:56 PM, Yonik Seeley <yo...@apache.org> wrote:
> On Thu, Nov 20, 2008 at 7:41 AM, Marc Sturlese <ma...@gmail.com>
> wrote:
> > I have started working with an index divided in 3 shards. When I did a
> > distributed search I got an error with the fields that were not string or
> > text. I read that the error was due to BinaryResponseWriter and not
> > string/text empty fields.
>
> I think it's more the case that if you have an invalid field value, it
> could blow up at different points in different code paths. The root
> cause is still an invalid value in the field.
>
> -Yonik
>
--
Regards,
Ian Connor
1 Leighton St #605
Cambridge, MA 02141
Direct Line: +1 (978) 6333372
Call Center Phone: +1 (714) 239 3875 (24 hrs)
Mobile Phone: +1 (312) 218 3209
Fax: +1(770) 818 5697
Suisse Phone: +41 (0) 22 548 1664
Skype: ian.connor
Re: not string or text fields and shards
Posted by Yonik Seeley <yo...@apache.org>.
On Thu, Nov 20, 2008 at 7:41 AM, Marc Sturlese <ma...@gmail.com> wrote:
> I have started working with an index divided in 3 shards. When I did a
> distributed search I got an error with the fields that were not string or
> text. I read that the error was due to BinaryResponseWriter and not
> string/text empty fields.
I think it's more the case that if you have an invalid field value, it
could blow up at different points in different code paths. The root
cause is still an invalid value in the field.
-Yonik