Re: I found a sorting bug in solr/lucene

2011-07-29 Thread Chris Hostetter
: According to that bug list, there are other characters that break the : sorting function. Is there a list of safe characters I can use as a : delimiter? the safest field names to use (and most efficient to parse when sorting) are things that follow the the "id" semenatics in java (not includi

Re: I found a sorting bug in solr/lucene

2011-07-19 Thread Jason Toy
According to that bug list, there are other characters that break the sorting function. Is there a list of safe characters I can use as a delimiter? On Mon, Jul 18, 2011 at 1:31 PM, Chris Hostetter wrote: > > : When I try to sort by a column with a colon in it like > : "scores:rails_f", solr ha

Re: I found a sorting bug in solr/lucene

2011-07-18 Thread Chris Hostetter
: When I try to sort by a column with a colon in it like : "scores:rails_f", solr has cutoff the column name from the colon : forward so "scores:rails_f" becomes "scores" Yes, this bug was recently reported against the 3.x line, but no fix has yet been identified... https://issues.apache.org/j

Re: I found a sorting bug in solr/lucene

2011-07-18 Thread Jason Toy
I am using a fairly popular library (sunspot-solr for ruby) on top of solr that introduces the use of a colon, so I will modify the library, but I think there is still a bug as this stopped working in recent version of solr. Solr should also not allow the data into the doc in the first place if it

Re: I found a sorting bug in solr/lucene

2011-07-18 Thread Nicholas Chase
Seems to me that you wouldn't want to use a colon in a field name, since the search syntax uses it (ie, to find a document with foo = bar, you use foo:bar). I don't know whether that's actually prohibited, but that could be your problem. Nick On 7/18/2011 8:10 AM, Jason Toy wrote: Hi

I found a sorting bug in solr/lucene

2011-07-18 Thread Jason Toy
Hi all, I found a bug that exists in the 3.1 and in trunk, but not in 1.4.1 When I try to sort by a column with a colon in it like "scores:rails_f", solr has cutoff the column name from the colon forward so "scores:rails_f" becomes "scores" To test, I inserted this doc: In 1.4.1 I was able to