Thanks.
I just copied the config file under
solr/solr-8.6.0/server/solr/configsets/_default and made minor changes.
Tried the console - I think SKMF is doing it.
Regards,
Jayadevan
On Mon, Aug 24, 2020 at 5:45 PM Dominique Bejean
wrote:
> Hi,
>
> We need to know how is analyzed your catch_all
Hi,
We need to know how is analyzed your catch_all field at index and search
time.
I think you are using a stemming filter and "apache" is stemmed as "apach".
So "apache" and "apach" match the document and not "apac".
You can use the console in order to see how terms are removed or
transformed by
: András Bártházi
Sent: Tuesday, May 15, 2012 6:50 AM
To: solr-user@lucene.apache.org
Subject: Re: simple query help
Hi,
You should use parantheses, have you tried that?
q=(skcode:2021051 and flength:368.0) or (skcode:2021049 and
ent_no:1040970907)
http://robotlibrarian.billdueber.com/solr-and
Kirk
Sent: Tuesday, May 15, 2012 8:23 AM
To: solr-user@lucene.apache.org
Subject: RE: simple query help
Hi
If I understand the terms correctly, the search-handler was configured to
use "edismax".
The start of the configuration in the solrconfig.xml looks like this:
edismax
> But whether or not it was simply the act of restarting - I'm
> not sure. (I had also found out that "AND " and "OR" should
> be written in uppercase, but this made no difference until
> after I had restarted).
By the way, there is a control parameter for this.
"lowercaseOperators A Boolean
around is to place a space
between the left parenthesis and the field name.
See:
https://issues.apache.org/jira/browse/SOLR-3377
-- Jack Krupansky
-Original Message-
From: Peter Kirk
Sent: Tuesday, May 15, 2012 7:04 AM
To: solr-user@lucene.apache.org
Subject: RE: simple query help
ter
-Original Message-
From: Ahmet Arslan [mailto:iori...@yahoo.com]
Sent: 15. maj 2012 13:25
To: solr-user@lucene.apache.org
Subject: RE: simple query help
> It doesn't make a difference. But now I'm thinking there's something
> completely odd - and I wonder if it'
Hi,
it is AND (uppercase) not and (smallcase) (and OR instead of or).
Regards,
Peter
2012/5/15 András Bártházi :
> Hi,
>
> You should use parantheses, have you tried that?
> q=(skcode:2021051 and flength:368.0) or (skcode:2021049 and
> ent_no:1040970907)
>
> http://robotlibrarian.billdueber.com/
> It doesn't make a difference. But now I'm thinking there's
> something completely odd - and I wonder if it's necessary to
> use a special search-handler to achieve what I want.
>
> For example, if I execute
> q=(skcode:2021051 AND flength:368.0)
>
> I get no results. If I omit the parentheses
er@lucene.apache.org
Subject: Re: simple query help
Hi,
You should use parantheses, have you tried that?
q=(skcode:2021051 and flength:368.0) or (skcode:2021049 and
ent_no:1040970907)
http://robotlibrarian.billdueber.com/solr-and-boolean-operators/
Bye,
Andras
2012/5/15 Peter Kirk
> Hi
>
Hi,
You should use parantheses, have you tried that?
q=(skcode:2021051 and flength:368.0) or (skcode:2021049 and
ent_no:1040970907)
http://robotlibrarian.billdueber.com/solr-and-boolean-operators/
Bye,
Andras
2012/5/15 Peter Kirk
> Hi
>
> Can someone please give me some help with a simple q
On 4/25/07, Gal Nitzan <[EMAIL PROTECTED]> wrote:
When I search
Q=title:"dog%20da*"
...
Probably has to do with the way your "title" field is analyzed.
The best way to debug such problems is with the analyzer admin tool:
http://localhost:8983/solr/admin/analysis.jsp - that page will show
12 matches
Mail list logo