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 ashokc <as...@qualcomm.com> on 2008/11/20 22:03:30 UTC

solrQueryParser does not take effect - nightly build

Hi,

I have set

<solrQueryParser defaultOperator="AND"/>

but it is not taking effect. It continues to take it as OR. I am working
with the latest nightly build 11/20/2008

For a querry like

term1 term2

Debug shows

<str name="parsedquery">content:term1 content:term2>/str>

Bug?

Thanks

- ashok


-- 
View this message in context: http://www.nabble.com/solrQueryParser-does-not-take-effect---nightly-build-tp20609974p20609974.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: solrQueryParser does not take effect - nightly build

Posted by "Aleksander M. Stensby" <al...@integrasco.no>.
That sounds a bit strange. Did you do the changes in the schema.xml before  
starting the server? Because if you change it while it is running, it will  
by default delete and replace the file (discarding any changes you make).  
In other words, make sure the server is not running, make your changes and  
then start up the server. Apart from that, I can't really see any reason  
for this to not work...

- Aleks


On Thu, 20 Nov 2008 22:03:30 +0100, ashokc <as...@qualcomm.com> wrote:

>
> Hi,
>
> I have set
>
> <solrQueryParser defaultOperator="AND"/>
>
> but it is not taking effect. It continues to take it as OR. I am working
> with the latest nightly build 11/20/2008
>
> For a querry like
>
> term1 term2
>
> Debug shows
>
> <str name="parsedquery">content:term1 content:term2>/str>
>
> Bug?
>
> Thanks
>
> - ashok
>

Re: solrQueryParser does not take effect - nightly build

Posted by Koji Sekiguchi <ko...@r.email.ne.jp>.
Committed revision 719793.

Thank you for reporting this, ashok!

Koji


Koji Sekiguchi wrote:
> ashok,
>
> Hmm, this is a bug. It was accidentally introduced when SOLR-657 was 
> committed.
>
> http://svn.apache.org/viewvc/lucene/solr/trunk/src/java/org/apache/solr/search/LuceneQParserPlugin.java?p2=%2Flucene%2Fsolr%2Ftrunk%2Fsrc%2Fjava%2Forg%2Fapache%2Fsolr%2Fsearch%2FLuceneQParserPlugin.java&p1=%2Flucene%2Fsolr%2Ftrunk%2Fsrc%2Fjava%2Forg%2Fapache%2Fsolr%2Fsearch%2FLuceneQParserPlugin.java&r1=701485&r2=701484&view=diff&pathrev=701485 
>
>
> I'll fix it shortly.
>
> Thank you,
>
> Koji

Re: solrQueryParser does not take effect - nightly build

Posted by Koji Sekiguchi <ko...@r.email.ne.jp>.
ashok,

Hmm, this is a bug. It was accidentally introduced when SOLR-657 was 
committed.

http://svn.apache.org/viewvc/lucene/solr/trunk/src/java/org/apache/solr/search/LuceneQParserPlugin.java?p2=%2Flucene%2Fsolr%2Ftrunk%2Fsrc%2Fjava%2Forg%2Fapache%2Fsolr%2Fsearch%2FLuceneQParserPlugin.java&p1=%2Flucene%2Fsolr%2Ftrunk%2Fsrc%2Fjava%2Forg%2Fapache%2Fsolr%2Fsearch%2FLuceneQParserPlugin.java&r1=701485&r2=701484&view=diff&pathrev=701485

I'll fix it shortly.

Thank you,

Koji


ashokc wrote:
> Hi,
>
> I have set
>
> <solrQueryParser defaultOperator="AND"/>
>
> but it is not taking effect. It continues to take it as OR. I am working
> with the latest nightly build 11/20/2008
>
> For a querry like
>
> term1 term2
>
> Debug shows
>
> <str name="parsedquery">content:term1 content:term2>/str>
>
> Bug?
>
> Thanks
>
> - ashok
>
>
>