Your query is going against the default field (defined in schema.xml). Have
you tried a fielded search?
And it would best to start a new thread for new questions see:
http://people.apache.org/~hossman/#threadhijack
Best
Erick
On Mon, May 2, 2011 at 3:46 AM, Pratik wrote:
> Hi,
> Thanks for your
Hi,
Were you able to sort the results using alphaOnlySort ?
If yes what changes were made to the schema and data-config ?
Thanks
--
View this message in context:
http://lucene.472066.n3.nabble.com/solr-sorting-problem-tp486144p2889473.html
Sent from the Solr - User mailing list archive at Nabb
Hi,
Thanks for your reply.
I'm, using "commit=true" while indexing, and it does index the records and
show the number of records indexed.
The problem is that search yields 0 records ( numFound="0" ).
e.g.
00onappl
There are some entries for spell checking in my schema too.
e.g.
The S
Two scenarios:
1) you call the indexing API but do not call 'commit'. This makes data
visible to searching.
2) the default solrconfig has HTTP caching turned on. So you redo the
search url, and you get the old result. This is really really
annoying. And you have to change the configuration to speci
Hello,
I got over that problem but now i am facing a new problem.
Indexing works but search does not.
I used the following line in the schema:-
and
I'm trying to use the default "alphaOnlySort" in the sample schema.xml.
Database is MySQL, there is a column/field named ColXYZ
My data-
Let's see the query you submit. This looks like a typo or an
improperly specified field name
":foodDesc"
Best
Erick
On Fri, Apr 22, 2011 at 8:18 AM, Pratik wrote:
> Were you able to get it work .. if yes how ?
> I'm having almost the same problem.
>
> I used the " fieldType name="alphaOnlyS
Were you able to get it work .. if yes how ?
I'm having almost the same problem.
I used the " fieldType name="alphaOnlySort" class="solr.TextField" as in
the sample schema.xml , to define a field named "alphaname".
Then copied from one of the fields name "foodDescUS" to "alphaname".
When i
Savvas-Andreas Moysidis wrote:
> In my understanding sorting on a field for which analysis has yielded
> multiple terms just doesn't make sense..
> If you have document#1 with a field A which has the terms Epsilon, Alpha,
> and document#2 with field A which has the terms Beta, Delta and request
> a
Jonathan Rochkind [rochk...@jhu.edu] wrote:
> I too sometimes have similar use cases, and my best ideas about how to
> solve them involve using faceting --- you can facet on a multi-valued
> field, and you can sort facets--but you can only sort facets by "index
> order", a strict byte-by-byte sort.
You may not sort on a tokenized field. You may not sort on a multiValued
field. You can only have one term in a field.
If there are more search terms than documents, A) sorting doesn't mean
anything and B) Lucene will throw an exception.
Erick Erickson wrote:
In general, the behavior when so
Erick Erickson wrote:
> In general, the behavior when sorting is not predictable when
> sorting on a tokenized field, which "text" is. What would
> it mean to sort on a field with "erick" "Moazzam" as tokens
> in a single document? Should it be in the "e"s or the "m"s?
Might it be possible or reas
In general, the behavior when sorting is not predictable when
sorting on a tokenized field, which "text" is. What would
it mean to sort on a field with "erick" "Moazzam" as tokens
in a single document? Should it be in the "e"s or the "m"s?
That said, you probably want to watch out for case
Be
For anyone who faced the same problem, changing the field to string
from text worked!
-Moazzam
On Fri, Oct 22, 2010 at 8:50 AM, Moazzam Khan wrote:
> The field type of the first name and last name is text. Could that be
> why it's not sorting properly? I just changed it to string and started
> a
The field type of the first name and last name is text. Could that be
why it's not sorting properly? I just changed it to string and started
a full-import. Hopefully that will work.
Thanks,
Moazzam
On Thu, Oct 21, 2010 at 7:42 PM, Jayendra Patil
wrote:
> need additional information .
> Sorti
need additional information .
Sorting is easy in Solr just by passing the sort parameter
However, when it comes to text sorting it depends on how you analyse
and tokenize your fields
Sorting does not work on fields with multiple tokens.
http://wiki.apache.org/solr/FAQ#Why_Isn.27t_Sorting_Worki
riginal Message
>> From: pmg <[EMAIL PROTECTED]>
>> To: solr-user@lucene.apache.org
>> Sent: Thursday, May 22, 2008 10:19:52 PM
>> Subject: Re: solr sorting problem
>>
>>
>> I forgot to mention that I made changes to schema after indexing.
>
e.org
> Sent: Thursday, May 22, 2008 10:19:52 PM
> Subject: Re: solr sorting problem
>
>
> I forgot to mention that I made changes to schema after indexing.
>
>
> pmg wrote:
> >
> > I have problem sorting solr results. Here is my solr confi
I forgot to mention that I made changes to schema after indexing.
pmg wrote:
>
> I have problem sorting solr results. Here is my solr config
>
>
>
> stored="true"/>
>
>
>
>
>
>
>
> search query
>
> select/?&rows=100&start=0&q=artistId:100346%20AND%20type:trac
18 matches
Mail list logo
