Re: Query translation of User Fields

2014-05-25 Thread Jack Krupansky
. -- Jack Krupansky -Original Message- From: Yonik Seeley Sent: Sunday, May 25, 2014 10:58 AM To: solr-user@lucene.apache.org Subject: Re: Query translation of User Fields On Thu, May 22, 2014 at 10:56 AM, Jack Krupansky wrote: Hmmm... that doesn't sound like what I would

Re: Query translation of User Fields

2014-05-25 Thread Yonik Seeley
On Thu, May 22, 2014 at 10:56 AM, Jack Krupansky wrote: > Hmmm... that doesn't sound like what I would have expected - I would have > thought that Solr would throw an exception on the "user" field, rather than > simply treat it as a text keyword. No, I believe that's working as designed. edismax

RE: Query translation of User Fields

2014-05-25 Thread Liram Vardi
Subject: Re: Query translation of User Fields Hmmm... that doesn't sound like what I would have expected - I would have thought that Solr would throw an exception on the "user" field, rather than simply treat it as a text keyword. File a Jira. Either it's a bug or the doc is no

Re: Query translation of User Fields

2014-05-22 Thread Jack Krupansky
Original Message- From: Liram Vardi Sent: Thursday, May 22, 2014 10:50 AM To: solr-user@lucene.apache.org Subject: Query translation of User Fields Hi all, I have a question regarding the functionality of Edismax parser and its "User Field" feature. We are running Solr 4.4 on our se

Query translation of User Fields

2014-05-22 Thread Liram Vardi
Hi all, I have a question regarding the functionality of Edismax parser and its "User Field" feature. We are running Solr 4.4 on our server. For the query: "q= id:b* user:"Anna Collins"&defType=edismax&uf=* -user&rows=0" The parsed query (taken from query debug info) is: +((id:b* (text:user) (te