There are many layers to this, but for the config you posted (applying
index-time WDGF configured to both split and catentate tokens), the
fundamental issue is that Lucene doesn't index positionLength, so the
graph structure (and token adjacency information) of the token stream
is lost when it's
Please ignore this. It was a user error. I was pointing to the wrong
analyzer in my app's cfg file.
Steve
On Mon, Mar 26, 2018 at 10:17 AM, Steven White wrote:
> Setting "sow=true" didn't make a difference.
>
> Here is what I'm using now: http://localhost:8983/
>
Setting "sow=true" didn't make a difference.
Here is what I'm using now:
http://localhost:8983/solr/ccfts/select_test?q=%22record%20type%20session%22=json=true=true=true
And here is the output:
{
"responseHeader":{
"status":0,
"QTime":1,
"params":{
"q":"\"record type
Hello, Steven.
Have you tried sow=true?
see
https://lucene.apache.org/solr/guide/7_2/the-extended-dismax-query-parser.html
Anyway, you can start from debugQuery=true, then try to explore
explainOther, and get to Analysis page after all.
On Mon, Mar 26, 2018 at 3:10 AM, Steven White
Hi Parul,
You might find this useful : https://github.com/cominvent/exactmatch/
From: Parul Gupta(Knimbus) parulgp...@gmail.com
To: solr-user@lucene.apache.org
Sent: Tuesday, July 9, 2013 12:03 PM
Subject: Phrase search without stopwords
Hi solr-user!!!
I
Hi
I solve it by copying the field in a string field type.
And query on this field only.
Regards
David
Le 09/07/2013 11:03, Parul Gupta(Knimbus) a écrit :
Hi solr-user!!!
I have an issue
I want to know that is it possible to implement StopwordFilterFactory with
KeywordTokenizer?
example
Hey thanks.
Its some what works for me
--
View this message in context:
http://lucene.472066.n3.nabble.com/Phrase-search-without-stopwords-tp4076527p4076598.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hi Jason,
you could add this filter to the end of your analyzer :
http://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters#solr.PositionFilterFactory
That should solve your problem.
Ludovic.
-
Jouve
France.
--
View this message in context:
Hi, Ludovic
That's just what I'm looking for.
You're been a big help.
Thank you so much.
Jason.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Phrase-search-error-tp3423799p3423916.html
Sent from the Solr - User mailing list archive at Nabble.com.
In general, just escape things. See:
http://lucene.apache.org/java/2_4_0/queryparsersyntax.html#Escaping Special
Characters
http://lucene.apache.org/java/2_4_0/queryparsersyntax.html#Escaping Special
CharactersBut I have to say that you might want to consider carefully
whether
this is a good
You have to escape the special characters.Use the below method to escape
public static String escapeQueryChars(String s) {
StringBuilder sb = new StringBuilder();
for (int i = 0; i s.length(); i++) {
char c = s.charAt(i);
// These characters are part of the query syntax and
On 08/09/2010 12:21, Grijesh.singh wrote:
see the analysis.jsp with debug verbose and see what happens at index time
and search time during analysis with your data
Also u can use debugQuery=on for seeing what actually parsed query is.
-
Grijesh
I've found a first solution by myself,
: I'm trying to match Apple 2 but not Apple2 using phrase search, this is
why I have it quoted.
: I was under the impression --when I use phrase search-- all the
: analyzer magic would not apply, but it is!!! Otherwise, how would I
: search for a phrase?!
well .. yes ... even with phrase
Well, the WordDelimiterFilterFactory in your query analyzer clearly makes
Apple 2 out of Apple2, that's what it's for. If you're looking for an exact
match, use a string field. Check the output with the debugQuery=true parameter.
Cheers,
-Original message-
From: johnmu...@aol.com
Jelsma markus.jel...@buyways.nl
To: solr-user@lucene.apache.org
Sent: Mon, Aug 2, 2010 2:27 pm
Subject: RE: Phrase search
Well, the WordDelimiterFilterFactory in your query analyzer clearly makes
Apple
out of Apple2, that's what it's for. If you're looking for an exact match,
se a string field
/AnalyzersTokenizersTokenFilters#solr.WordDelimiterFilterFactory
Cheers,
-Original message-
From: johnmu...@aol.com
Sent: Mon 02-08-2010 21:29
To: solr-user@lucene.apache.org;
Subject: Re: Phrase search
Thanks for the quick response.
Which part of my WordDelimiterFilterFactory is changing
, 2010 3:54 pm
Subject: RE: Re: Phrase search
Hi,
Queries on an analyzed field will need to be analyzed as well or it might not
atch. You can configure the WordDelimiterFilterFactory so it will not split
nto multiple tokens because of numerics, see the splitOnNumerics parameter [1].
[1]:
http
: I don't understand why i'm getting this behavior. I was under the
: impression if I search for Apple 2 (with quotes and space before “2”)
: it will give me different results vs. if I search for Apple2 (with
: quotes and no space before “2”), but I'm not! Why?
if you search Apple 2 in
I wanted to do phrase search. What are the analyzers
that best suited for phrase search. I tried with
textgen, but it did not yield the expected results.
I wanted to index:
my dear friend
If I search for dear friend, I should get the result and
if I search for friend dear I should
Check out
http://wiki.apache.org/solr/DisMaxRequestHandler
http://wiki.apache.org/solr/DisMaxRequestHandlerIt's partially a function
of the field type (textGen) in your case but it's also a function of how you
handle matches on the fields you care about.
- Amit
On Sun, May 2, 2010 at 8:30 PM,
This problem is related with the default operator in dismax. Currently OR is
the default operator and it is behaving perfectly fine. I have changed the
default operator in schema.xml to AND, I also have changed the minimum match
to 100%.
But it seems like AND as default operator doesnt work with
, 2009 3:48:45 AM
Subject: Re: Phrase Search Issue
This problem is related with the default operator in dismax. Currently OR is
the default operator and it is behaving perfectly fine. I have changed the
default operator in schema.xml to AND, I also have changed the minimum match
to 100
22 matches
Mail list logo