RE: Wildcard search not working
Hi Ahmet, Hi Upayavira,
OK, it seems that I have to dive a bit deeper in the Solr filters and
tokenizers. I've just realized that my command there is too limited.
Thanks a lot guys so far for help. Cheers and have a nice day,
christian
-Original Message-
From: Ahmet Arslan [mailto:iori...@yahoo.com]
Sent: Freitag, 12. August 2016 07:41
To: solr-user@lucene.apache.org; Ribeaud, Christian (Ext)
Subject: Re: Wildcard search not working
Hi Christian,
Please use the following filter before/above the stemmer.
Plus, you may want to add :
Ahmet
On Thursday, August 11, 2016 9:31 PM, "Ribeaud, Christian (Ext)"
wrote:
Hi Ahmet,
Many thanks for your reply. I had a look at the URL you pointed out but,
honestly, I have to admit that I did not fully understand you.
Let's be a bit more concrete. Following the schema snippet for the
corresponding field:
...
...
What is wrong with this schema? Respectively, what should I change to be able
to correctly do wildcard searches?
Many thanks for your time. Cheers,
christian
--
Christian Ribeaud
Software Engineer (External)
NIBR / WSJ-310.5.17
Novartis Campus
CH-4056 Basel
-Original Message-
From: Ahmet Arslan [mailto:iori...@yahoo.com]
Sent: Donnerstag, 11. August 2016 16:00
To: solr-user@lucene.apache.org; Ribeaud, Christian (Ext)
Subject: Re: Wildcard search not working
Hi Chiristian,
The query r?che may not return at least the same number of matches as roche
depending on your analysis chain.
The difference is roche is analyzed but r?che don't. Wildcard queries are
executed on the indexed/analyzed terms.
For example, if roche is indexed/analyzed as roch, the query r?che won't match
it.
Please see : https://wiki.apache.org/solr/MultitermQueryAnalysis
Ahmet
On Thursday, August 11, 2016 4:42 PM, "Ribeaud, Christian (Ext)"
wrote:
Hi,
What would be the reasons making the wildcard search for Lucene Query Parser
NOT working?
We are using Solr 5.4.1 and, using the admin console, I am triggering for
instance searches with term 'roche' in a specific core. Everything fine, I am
getting for instance two matches. I would expect at least the same number of
matches with term 'r?che'. However, this does NOT happen. I am getting zero
matches. Same problem occurs with 'r*che'. 'roch?' does not work neither but
'roch*' works.
Switching debug mode brings following output:
"debug": {
"rawquerystring": "roch?",
"querystring": "roch?",
"parsedquery": "text:roch?",
"parsedquery_toString": "text:roch?",
"explain": {},
"QParser": "LuceneQParser",
...
Any idea? Thanks and cheers,
christian
Re: Wildcard search not working
Hi Christian,
Please use the following filter before/above the stemmer.
Plus, you may want to add :
Ahmet
On Thursday, August 11, 2016 9:31 PM, "Ribeaud, Christian (Ext)"
wrote:
Hi Ahmet,
Many thanks for your reply. I had a look at the URL you pointed out but,
honestly, I have to admit that I did not fully understand you.
Let's be a bit more concrete. Following the schema snippet for the
corresponding field:
...
...
What is wrong with this schema? Respectively, what should I change to be able
to correctly do wildcard searches?
Many thanks for your time. Cheers,
christian
--
Christian Ribeaud
Software Engineer (External)
NIBR / WSJ-310.5.17
Novartis Campus
CH-4056 Basel
-Original Message-
From: Ahmet Arslan [mailto:iori...@yahoo.com]
Sent: Donnerstag, 11. August 2016 16:00
To: solr-user@lucene.apache.org; Ribeaud, Christian (Ext)
Subject: Re: Wildcard search not working
Hi Chiristian,
The query r?che may not return at least the same number of matches as roche
depending on your analysis chain.
The difference is roche is analyzed but r?che don't. Wildcard queries are
executed on the indexed/analyzed terms.
For example, if roche is indexed/analyzed as roch, the query r?che won't match
it.
Please see : https://wiki.apache.org/solr/MultitermQueryAnalysis
Ahmet
On Thursday, August 11, 2016 4:42 PM, "Ribeaud, Christian (Ext)"
wrote:
Hi,
What would be the reasons making the wildcard search for Lucene Query Parser
NOT working?
We are using Solr 5.4.1 and, using the admin console, I am triggering for
instance searches with term 'roche' in a specific core. Everything fine, I am
getting for instance two matches. I would expect at least the same number of
matches with term 'r?che'. However, this does NOT happen. I am getting zero
matches. Same problem occurs with 'r*che'. 'roch?' does not work neither but
'roch*' works.
Switching debug mode brings following output:
"debug": {
"rawquerystring": "roch?",
"querystring": "roch?",
"parsedquery": "text:roch?",
"parsedquery_toString": "text:roch?",
"explain": {},
"QParser": "LuceneQParser",
...
Any idea? Thanks and cheers,
christian
Re: Wildcard search not working
You have a stemming filter in your analysis chain. Go to the analysis
tab, select the 'text' field, and put "Roche" into both boxes. Click
analyse. I bet you you will see Roch, not Roche, because of your
stemming filter shown below.
That's what Ahmet shrewdly identified above.
Upayavira
On Thu, 11 Aug 2016, at 08:31 PM, Ribeaud, Christian (Ext) wrote:
> Hi Ahmet,
>
> Many thanks for your reply. I had a look at the URL you pointed out but,
> honestly, I have to admit that I did not fully understand you.
> Let's be a bit more concrete. Following the schema snippet for the
> corresponding field:
>
> ...
> required="false" multiValued="false" />
>
>
> positionIncrementGap="100">
>
>
>
> words="lang/stopwords_de.txt" format="snowball" />
>
>
>
>
>
>
> ...
>
> What is wrong with this schema? Respectively, what should I change to be
> able to correctly do wildcard searches?
>
> Many thanks for your time. Cheers,
>
> christian
> --
> Christian Ribeaud
> Software Engineer (External)
> NIBR / WSJ-310.5.17
> Novartis Campus
> CH-4056 Basel
>
>
> -----Original Message-
> From: Ahmet Arslan [mailto:iori...@yahoo.com]
> Sent: Donnerstag, 11. August 2016 16:00
> To: solr-user@lucene.apache.org; Ribeaud, Christian (Ext)
> Subject: Re: Wildcard search not working
>
> Hi Chiristian,
>
> The query r?che may not return at least the same number of matches as
> roche depending on your analysis chain.
> The difference is roche is analyzed but r?che don't. Wildcard queries are
> executed on the indexed/analyzed terms.
> For example, if roche is indexed/analyzed as roch, the query r?che won't
> match it.
>
> Please see : https://wiki.apache.org/solr/MultitermQueryAnalysis
>
> Ahmet
>
>
>
> On Thursday, August 11, 2016 4:42 PM, "Ribeaud, Christian (Ext)"
> wrote:
> Hi,
>
> What would be the reasons making the wildcard search for Lucene Query
> Parser NOT working?
>
> We are using Solr 5.4.1 and, using the admin console, I am triggering for
> instance searches with term 'roche' in a specific core. Everything fine,
> I am getting for instance two matches. I would expect at least the same
> number of matches with term 'r?che'. However, this does NOT happen. I am
> getting zero matches. Same problem occurs with 'r*che'. 'roch?' does not
> work neither but 'roch*' works.
>
> Switching debug mode brings following output:
>
> "debug": {
> "rawquerystring": "roch?",
> "querystring": "roch?",
> "parsedquery": "text:roch?",
> "parsedquery_toString": "text:roch?",
> "explain": {},
> "QParser": "LuceneQParser",
> ...
>
> Any idea? Thanks and cheers,
>
> christian
RE: Wildcard search not working
Hi Ahmet,
Many thanks for your reply. I had a look at the URL you pointed out but,
honestly, I have to admit that I did not fully understand you.
Let's be a bit more concrete. Following the schema snippet for the
corresponding field:
...
...
What is wrong with this schema? Respectively, what should I change to be able
to correctly do wildcard searches?
Many thanks for your time. Cheers,
christian
--
Christian Ribeaud
Software Engineer (External)
NIBR / WSJ-310.5.17
Novartis Campus
CH-4056 Basel
-Original Message-
From: Ahmet Arslan [mailto:iori...@yahoo.com]
Sent: Donnerstag, 11. August 2016 16:00
To: solr-user@lucene.apache.org; Ribeaud, Christian (Ext)
Subject: Re: Wildcard search not working
Hi Chiristian,
The query r?che may not return at least the same number of matches as roche
depending on your analysis chain.
The difference is roche is analyzed but r?che don't. Wildcard queries are
executed on the indexed/analyzed terms.
For example, if roche is indexed/analyzed as roch, the query r?che won't match
it.
Please see : https://wiki.apache.org/solr/MultitermQueryAnalysis
Ahmet
On Thursday, August 11, 2016 4:42 PM, "Ribeaud, Christian (Ext)"
wrote:
Hi,
What would be the reasons making the wildcard search for Lucene Query Parser
NOT working?
We are using Solr 5.4.1 and, using the admin console, I am triggering for
instance searches with term 'roche' in a specific core. Everything fine, I am
getting for instance two matches. I would expect at least the same number of
matches with term 'r?che'. However, this does NOT happen. I am getting zero
matches. Same problem occurs with 'r*che'. 'roch?' does not work neither but
'roch*' works.
Switching debug mode brings following output:
"debug": {
"rawquerystring": "roch?",
"querystring": "roch?",
"parsedquery": "text:roch?",
"parsedquery_toString": "text:roch?",
"explain": {},
"QParser": "LuceneQParser",
...
Any idea? Thanks and cheers,
christian
Re: Wildcard search not working
Hi Chiristian,
The query r?che may not return at least the same number of matches as roche
depending on your analysis chain.
The difference is roche is analyzed but r?che don't. Wildcard queries are
executed on the indexed/analyzed terms.
For example, if roche is indexed/analyzed as roch, the query r?che won't match
it.
Please see : https://wiki.apache.org/solr/MultitermQueryAnalysis
Ahmet
On Thursday, August 11, 2016 4:42 PM, "Ribeaud, Christian (Ext)"
wrote:
Hi,
What would be the reasons making the wildcard search for Lucene Query Parser
NOT working?
We are using Solr 5.4.1 and, using the admin console, I am triggering for
instance searches with term 'roche' in a specific core. Everything fine, I am
getting for instance two matches. I would expect at least the same number of
matches with term 'r?che'. However, this does NOT happen. I am getting zero
matches. Same problem occurs with 'r*che'. 'roch?' does not work neither but
'roch*' works.
Switching debug mode brings following output:
"debug": {
"rawquerystring": "roch?",
"querystring": "roch?",
"parsedquery": "text:roch?",
"parsedquery_toString": "text:roch?",
"explain": {},
"QParser": "LuceneQParser",
...
Any idea? Thanks and cheers,
christian
Wildcard search not working
Hi,
What would be the reasons making the wildcard search for Lucene Query Parser
NOT working?
We are using Solr 5.4.1 and, using the admin console, I am triggering for
instance searches with term 'roche' in a specific core. Everything fine, I am
getting for instance two matches. I would expect at least the same number of
matches with term 'r?che'. However, this does NOT happen. I am getting zero
matches. Same problem occurs with 'r*che'. 'roch?' does not work neither but
'roch*' works.
Switching debug mode brings following output:
"debug": {
"rawquerystring": "roch?",
"querystring": "roch?",
"parsedquery": "text:roch?",
"parsedquery_toString": "text:roch?",
"explain": {},
"QParser": "LuceneQParser",
...
Any idea? Thanks and cheers,
christian
Re: Wildcard search not working with search term having special characters and digits
Can someone help me out with this issue please? -- View this message in context: http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-with-search-term-having-special-characters-and-digits-tp4133385p4133770.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Wildcard search not working with search term having special characters and digits
Thanks jack for prompt response! So is there any solution to make this scenario works? Or wildcard doesn't work with special characters and numerics? Thanks, G. Naresh Kumar -- View this message in context: http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-with-search-term-having-special-characters-and-digits-tp4133385p4133554.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Wildcard search not working with search term having special characters and digits
Wildcard query only works for single terms. Any embedded special characters will cause a term to be split into multiple terms at index time. The use of a wildcard in a query term with embedded special characters will bypass normal analysis - you need to enter the term exactly as it would be analyzed at index time for wildcard to work. Ditto is your filed type uses the word delimiter filter with the split digits option enabled - the alpha and numeric portions will generate separate terms - and cause a wildcard to fail. -- Jack Krupansky -Original Message- From: Geepalem Sent: Sunday, April 27, 2014 3:30 PM To: solr-user@lucene.apache.org Subject: Wildcard search not working with search term having special characters and digits Hi, Below query without wildcard search is returning results. http://localhost:8080/solr/master/select?q=page_title_t:"an-138"; But below query with wildcard is not returning results http://localhost:8080/solr/master/select?q=page_title_t:"an-13*"; Below query with wildcard search and no didgits is returning results. http://localhost:8080/solr/master/select?q=page_title_t:"an-*"; I have tried by adding WordDelimeter Filter but there is no luck. Please suggest or guide how to make wildcard search works with special characters and digits. Appreciate immediate response!! Thanks, G. Naresh Kumar -- View this message in context: http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-with-search-term-having-special-characters-and-digits-tp4133385.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Wildcard search not working with search term having special characters and digits
Can some one please help me with this as I am struck with this issue.. -- View this message in context: http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-with-search-term-having-special-characters-and-digits-tp4133385p4133478.html Sent from the Solr - User mailing list archive at Nabble.com.
Wildcard search not working with search term having special characters and digits
Hi, Below query without wildcard search is returning results. http://localhost:8080/solr/master/select?q=page_title_t:"an-138"; But below query with wildcard is not returning results http://localhost:8080/solr/master/select?q=page_title_t:"an-13*"; Below query with wildcard search and no didgits is returning results. http://localhost:8080/solr/master/select?q=page_title_t:"an-*"; I have tried by adding WordDelimeter Filter but there is no luck. Please suggest or guide how to make wildcard search works with special characters and digits. Appreciate immediate response!! Thanks, G. Naresh Kumar -- View this message in context: http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-with-search-term-having-special-characters-and-digits-tp4133385.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Wildcard search not working if the query contains numbers along with special characters.
Hi,
Forget about patternReplaceCharFilter for a moment. Your example is more clear
this time.
q=titleName:1999/99*
should return following two docs:
d1) JULIUS CAESER (1999/99)
d2) ARABIAN NIGHTS - 1999/99
This is achievable with the following type.
1) MappingCharFilterFactory with mappings.txt
"(" => ""
")" => ""
2) WhiteSpaceTokenizerFactory
3) LowercaseFilterFactory
I dont understand your sentence : "i will never be able to specifically search
the title i want as 1999/99."
But please try / test above. I also suggest you to use prefix query parser.
https://cwiki.apache.org/confluence/display/solr/Other+Parsers#OtherParsers-PrefixQueryParser
Ahmet
On Wednesday, March 5, 2014 11:20 PM, Kashish wrote:
Hi Ahmet,
Let me explain with another scenario .
There is a title -> ARABIAN NIGHTS - 1999/99
Now in autocomplete, if i give 1999/99 , in the backend i append an asterisk
to it and form the solr url thsi way
q=titleName:1999/99*
I get the above mentioned title.- so works perfect
Now lets add another title to this.
-> JULIUS CAESER (1999/99)
If i pass the same query parameter, i would definitely expect both these
titles to come up. but this new one doesn't come(Because of the braces).
I can add patternReplaceFilter but this way i will never be able to
specifically search the title i want as 1999/99.
Hope you get what i am trying to achieve. Is my understanding wrong
somewhere?
Thanks.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-if-the-query-conatins-numbers-along-with-special-characters-tp4119608p4121512.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Wildcard search not working if the query contains numbers along with special characters.
Hi Ahmet, Let me explain with another scenario . There is a title -> ARABIAN NIGHTS - 1999/99 Now in autocomplete, if i give 1999/99 , in the backend i append an asterisk to it and form the solr url thsi way q=titleName:1999/99* I get the above mentioned title.- so works perfect Now lets add another title to this. -> JULIUS CAESER (1999/99) If i pass the same query parameter, i would definitely expect both these titles to come up. but this new one doesn't come(Because of the braces). I can add patternReplaceFilter but this way i will never be able to specifically search the title i want as 1999/99. Hope you get what i am trying to achieve. Is my understanding wrong somewhere? Thanks. -- View this message in context: http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-if-the-query-conatins-numbers-along-with-special-characters-tp4119608p4121512.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Wildcard search not working if the query contains numbers along with special characters.
Hi Kashish, This is confusing. You gave the following example : query 1999/99* should return RABIAN NIGHTS #01 (1999/99) However you said "I cannot ignore parenthesis or other special characters..." Above two contadicts each other. Since you are after autocomplete you might be interested in this http://www.cominvent.com/2012/01/25/super-flexible-autocomplete-with-solr/ Ahmet On Wednesday, March 5, 2014 8:36 PM, Kashish wrote: Hi, Pls help me with this. -- View this message in context: http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-if-the-query-conatins-numbers-along-with-special-characters-tp4119608p4121457.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Wildcard search not working if the query contains numbers along with special characters.
Hi, Pls help me with this. -- View this message in context: http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-if-the-query-conatins-numbers-along-with-special-characters-tp4119608p4121457.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Wildcard search not working if the query contains numbers along with special characters.
Hi Erick, I understand what you pointing out but the thing is.. this is for autocomplete feature. I cannot ignore parenthesis or other special characters as in certain titles like 'A Team of five', if the user fives 'a team' then titles containing a-team and rest also comes off and this one gets lost as we show only top 6 results (user can drill down to get closer to the result he wants). I modified my fieldtype so at index added worddelimeter delimeter and at query time added patternfilter but now still if i use asterisk i get no records for 1999/99* but get without asterisk. Thsi is not what i want as by default, whatever the user enters we append asterisk to it for autocomplete search. Thanks -- View this message in context: http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-if-the-query-conatins-numbers-along-with-special-characters-tp4119608p4121205.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Wildcard search not working if the query contains numbers along with special characters.
The admin/analysis page is your friend. Taking some time to get acquainted with that page will save you lots and lots and lots of time. In this case, you'd have seen that your input is actually tokenized as (1999/99), parentheses and all as a _single_ token, so of course searching for 1999/99 wouldn't work. Searching for *1999/99* is generally a bad idea. It'll work, but it's a kludge. What you _do_ need to do is define your use-cases. Let's assume that you _never_ want parentheses to be relevant. You could use PatternReplaceCharFilterFactory or PatternReplaceFilterFactory in both index and query parts of your analysis chain to remove parens. Or really any kinds of extraneous characters you decided were unimportant. But you need to decide what's "important" and enforce that. Best, Erick On Tue, Feb 25, 2014 at 7:28 PM, Kashish wrote: > Hi Ahmet/Erick, > > I tried escaping as well. See no luck. > > The title am looking for is - ARABIAN NIGHTS #01 (1999/99) > > I figured out that if i pass the query as *1999/99* (i.e asterisk not only > at the end but at the beginning as well), It works. > > The problem is the braces. I can change my field type and add > > generateNumberParts="1" catenateWords="1" catenateNumbers="1" > catenateAll="0" splitOnCaseChange="1" preserveOriginal="1"/> > > But this will show too many results in autocomplete. > > Is there any best way to handle this? Or should i pass asterisk before and > after the query? > > Thanks. > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-if-the-query-conatins-numbers-along-with-special-characters-tp4119608p4119678.html > Sent from the Solr - User mailing list archive at Nabble.com. >
Re: Wildcard search not working if the query contains numbers along with special characters.
Hi Ahmet/Erick, I tried escaping as well. See no luck. The title am looking for is - ARABIAN NIGHTS #01 (1999/99) I figured out that if i pass the query as *1999/99* (i.e asterisk not only at the end but at the beginning as well), It works. The problem is the braces. I can change my field type and add But this will show too many results in autocomplete. Is there any best way to handle this? Or should i pass asterisk before and after the query? Thanks. -- View this message in context: http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-if-the-query-conatins-numbers-along-with-special-characters-tp4119608p4119678.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Wildcard search not working if the query contains numbers along with special characters.
Hi, By saying escaping I mean this : q=title_autocomplete:1999\/99* It is different than URL encoding. http://lucene.apache.org/core/4_6_0/queryparser/org/apache/lucene/queryparser/classic/package-summary.html#Escaping_Special_Characters If prefix query parser didn't return what you want then it must be something with indexed terms. Can you give an example raw documents text that you expect to retrieve with this query? On Tuesday, February 25, 2014 10:15 PM, Kashish wrote: Hi Ahmet, Thanks for your reply. Yes. I pass my query this way - > q=title_autocomplete:1999%2f99 I tried your way too. But no luck. :( -- View this message in context: http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-if-the-query-conatins-numbers-along-with-special-characters-tp4119608p4119615.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Wildcard search not working if the query conatins numbers along with special characters.
What does it say happens on your admin/analysis page
for that field?
And did you by any chance change your schema without
reindexing everything?
Also, try the TermsComonent to see what tokens are actually
_in_ your index. Schema-browser from the admin page can
help here too.
Best,
Erick
On Tue, Feb 25, 2014 at 12:05 PM, Ahmet Arslan wrote:
> Hi Kashish,
>
>
> What happens when you use this q={!prefix f=title_autocomplete}1999/99
>
> I suspect '/' character is a special query parser character therefore it
> needs to be escaped.
>
> Ahmet
>
>
> On Tuesday, February 25, 2014 9:55 PM, Kashish
> wrote:
> Hi,
>
> I have a very weird problem. The wild card search works fine for all
> scenarios but one. It doesn't seem to give any result for query 1999/99*. I
> checked the debug query and its formed perfect.
>
> title_autocomplete:1999/99*
> title_autocomplete:1999/99*
> (+title_autocomplete:1999/99* ())/no_coord
> +title_autocomplete:1999/99* ()
>
> This is my fieldType
>
> positionIncrementGap="100">
>
>
> words="stopwords.txt" enablePositionIncrements="true" />
>
>
>
>
>
> words="stopwords.txt" enablePositionIncrements="true" />
>
>
>
>
>
>
> Please help we with this.
>
> Thanks.
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-if-the-query-conatins-numbers-along-with-special-characters-tp4119608.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
>
Re: Wildcard search not working if the query contains numbers along with special characters.
Hi Ahmet, Thanks for your reply. Yes. I pass my query this way - > q=title_autocomplete:1999%2f99 I tried your way too. But no luck. :( -- View this message in context: http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-if-the-query-conatins-numbers-along-with-special-characters-tp4119608p4119615.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Wildcard search not working if the query conatins numbers along with special characters.
Hi Kashish,
What happens when you use this q={!prefix f=title_autocomplete}1999/99
I suspect '/' character is a special query parser character therefore it needs
to be escaped.
Ahmet
On Tuesday, February 25, 2014 9:55 PM, Kashish
wrote:
Hi,
I have a very weird problem. The wild card search works fine for all
scenarios but one. It doesn't seem to give any result for query 1999/99*. I
checked the debug query and its formed perfect.
title_autocomplete:1999/99*
title_autocomplete:1999/99*
(+title_autocomplete:1999/99* ())/no_coord
+title_autocomplete:1999/99* ()
This is my fieldType
Please help we with this.
Thanks.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-if-the-query-conatins-numbers-along-with-special-characters-tp4119608.html
Sent from the Solr - User mailing list archive at Nabble.com.
Wildcard search not working if the query conatins numbers along with special characters.
Hi, I have a very weird problem. The wild card search works fine for all scenarios but one. It doesn't seem to give any result for query 1999/99*. I checked the debug query and its formed perfect. title_autocomplete:1999/99* title_autocomplete:1999/99* (+title_autocomplete:1999/99* ())/no_coord +title_autocomplete:1999/99* () This is my fieldType Please help we with this. Thanks. -- View this message in context: http://lucene.472066.n3.nabble.com/Wildcard-search-not-working-if-the-query-conatins-numbers-along-with-special-characters-tp4119608.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Wildcard search not working if full word is queried
Celso You are very welcome and yes I should have mentioned that wildcard searches are not analyzed (which is a recurring theme). This also means that they are not downcased, so the search TEST* will probably not find anything either in your set up. Cheers François On Jul 1, 2011, at 5:16 AM, Celso Pinto wrote: > Hi again, > > read (past tense) TFM :-) and: > > "On wildcard and fuzzy searches, no text analysis is performed on the > search word." > > Thanks a lot François! > > Regards, > Celso > > On Fri, Jul 1, 2011 at 10:02 AM, Celso Pinto wrote: >> Hi François, >> >> it is indeed being stemmed, thanks a lot for the heads up. It appears >> that stemming is also configured for the query so it should work just >> the same, no? >> >> Thanks again. >> >> Regards, >> Celso >> >> >> 2011/6/30 François Schiettecatte : >>> I would run that word through the analyzer, I suspect that the word 'teste' >>> is being stemmed to 'test' in the index, at least that is the first place I >>> would check. >>> >>> François >>> >>> On Jun 30, 2011, at 2:21 PM, Celso Pinto wrote: >>> Hi everyone, I'm having some trouble figuring out why a query with an exact word followed by the * wildcard, eg. teste*, returns no results while a query for test* returns results that have the word "teste" in them. I've created a couple of pasties: Exact word with wildcard : http://pastebin.com/n9SMNsH0 Similar word: http://pastebin.com/jQ56Ww6b Parameters other than title, description and content have no effect other than filtering out unwanted results. In a two of the four results, the title has the complete word "teste". On the other two, the word appears in the other fields. Does anyone have any insights about what I'm doing wrong? Thanks in advance. Regards, Celso >>> >>> >>
Re: Wildcard search not working if full word is queried
Hi again, read (past tense) TFM :-) and: "On wildcard and fuzzy searches, no text analysis is performed on the search word." Thanks a lot François! Regards, Celso On Fri, Jul 1, 2011 at 10:02 AM, Celso Pinto wrote: > Hi François, > > it is indeed being stemmed, thanks a lot for the heads up. It appears > that stemming is also configured for the query so it should work just > the same, no? > > Thanks again. > > Regards, > Celso > > > 2011/6/30 François Schiettecatte : >> I would run that word through the analyzer, I suspect that the word 'teste' >> is being stemmed to 'test' in the index, at least that is the first place I >> would check. >> >> François >> >> On Jun 30, 2011, at 2:21 PM, Celso Pinto wrote: >> >>> Hi everyone, >>> >>> I'm having some trouble figuring out why a query with an exact word >>> followed by the * wildcard, eg. teste*, returns no results while a >>> query for test* returns results that have the word "teste" in them. >>> >>> I've created a couple of pasties: >>> >>> Exact word with wildcard : http://pastebin.com/n9SMNsH0 >>> Similar word: http://pastebin.com/jQ56Ww6b >>> >>> Parameters other than title, description and content have no effect >>> other than filtering out unwanted results. In a two of the four >>> results, the title has the complete word "teste". On the other two, >>> the word appears in the other fields. >>> >>> Does anyone have any insights about what I'm doing wrong? >>> >>> Thanks in advance. >>> >>> Regards, >>> Celso >> >> >
Re: Wildcard search not working if full word is queried
Hi François, it is indeed being stemmed, thanks a lot for the heads up. It appears that stemming is also configured for the query so it should work just the same, no? Thanks again. Regards, Celso 2011/6/30 François Schiettecatte : > I would run that word through the analyzer, I suspect that the word 'teste' > is being stemmed to 'test' in the index, at least that is the first place I > would check. > > François > > On Jun 30, 2011, at 2:21 PM, Celso Pinto wrote: > >> Hi everyone, >> >> I'm having some trouble figuring out why a query with an exact word >> followed by the * wildcard, eg. teste*, returns no results while a >> query for test* returns results that have the word "teste" in them. >> >> I've created a couple of pasties: >> >> Exact word with wildcard : http://pastebin.com/n9SMNsH0 >> Similar word: http://pastebin.com/jQ56Ww6b >> >> Parameters other than title, description and content have no effect >> other than filtering out unwanted results. In a two of the four >> results, the title has the complete word "teste". On the other two, >> the word appears in the other fields. >> >> Does anyone have any insights about what I'm doing wrong? >> >> Thanks in advance. >> >> Regards, >> Celso > >
Re: Wildcard search not working if full word is queried
I would run that word through the analyzer, I suspect that the word 'teste' is being stemmed to 'test' in the index, at least that is the first place I would check. François On Jun 30, 2011, at 2:21 PM, Celso Pinto wrote: > Hi everyone, > > I'm having some trouble figuring out why a query with an exact word > followed by the * wildcard, eg. teste*, returns no results while a > query for test* returns results that have the word "teste" in them. > > I've created a couple of pasties: > > Exact word with wildcard : http://pastebin.com/n9SMNsH0 > Similar word: http://pastebin.com/jQ56Ww6b > > Parameters other than title, description and content have no effect > other than filtering out unwanted results. In a two of the four > results, the title has the complete word "teste". On the other two, > the word appears in the other fields. > > Does anyone have any insights about what I'm doing wrong? > > Thanks in advance. > > Regards, > Celso
Wildcard search not working if full word is queried
Hi everyone, I'm having some trouble figuring out why a query with an exact word followed by the * wildcard, eg. teste*, returns no results while a query for test* returns results that have the word "teste" in them. I've created a couple of pasties: Exact word with wildcard : http://pastebin.com/n9SMNsH0 Similar word: http://pastebin.com/jQ56Ww6b Parameters other than title, description and content have no effect other than filtering out unwanted results. In a two of the four results, the title has the complete word "teste". On the other two, the word appears in the other fields. Does anyone have any insights about what I'm doing wrong? Thanks in advance. Regards, Celso
Re: embedded wildcard search not working?
Some of the wildcards work, but not all of them. Unsurprisingly, the ones that seem to work are ones that are wildcards in the 'base' of the word. Thanks for the tip on the lowercase before stop words. On Wed, Feb 18, 2009 at 12:35 AM, Otis Gospodnetic < otis_gospodne...@yahoo.com> wrote: > Jim, > > Does app*l or even a*p* work? Perhaps "apple" gets stemmed to something > that doesn't end in "e", such as "appl"? > Regarding your config, you probably want to lowercase before removing stop > words, so you'll want to change the order of those filters a bit. That's > not related to your wildcard question. > > Otis -- > Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch > > > > > > From: Jim Adams > To: solr-user@lucene.apache.org > Sent: Wednesday, February 18, 2009 6:30:22 AM > Subject: embedded wildcard search not working? > > This is a straightforward question, but I haven't been able to figure out > what is up with my application. > > I seem to be able to search on trailing wildcards just find. For example, > fieldName:a* will return documents with apple, ardvaark, etc. in them. But > if I was to try and search on a field containing 'apple' with 'a*e' I would > return nothing. > > My gut is telling me that I should be using a different data type or a > different filter option. Here is how my text type is defined: > > > > > words="stopwords.txt"/> > generateWordParts="1" generateNumberParts="1" catenateWords="1" > catenateNumbers="1" catenateAll="0" /> > > protected="protwords.txt"/> > > > > > synonyms="synonyms.txt" ignoreCase="true" expand="true"/> > words="stopwords.txt"/> > generateWordParts="1" generateNumberParts="1" catenateWords="0" > catenateNumbers="0" catenateAll="0"/> > > protected="protwords.txt"/> > > > > Thanks for your help. > >
Re: embedded wildcard search not working?
Jim, Does app*l or even a*p* work? Perhaps "apple" gets stemmed to something that doesn't end in "e", such as "appl"? Regarding your config, you probably want to lowercase before removing stop words, so you'll want to change the order of those filters a bit. That's not related to your wildcard question. Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch From: Jim Adams To: solr-user@lucene.apache.org Sent: Wednesday, February 18, 2009 6:30:22 AM Subject: embedded wildcard search not working? This is a straightforward question, but I haven't been able to figure out what is up with my application. I seem to be able to search on trailing wildcards just find. For example, fieldName:a* will return documents with apple, ardvaark, etc. in them. But if I was to try and search on a field containing 'apple' with 'a*e' I would return nothing. My gut is telling me that I should be using a different data type or a different filter option. Here is how my text type is defined: Thanks for your help.
embedded wildcard search not working?
This is a straightforward question, but I haven't been able to figure out what is up with my application. I seem to be able to search on trailing wildcards just find. For example, fieldName:a* will return documents with apple, ardvaark, etc. in them. But if I was to try and search on a field containing 'apple' with 'a*e' I would return nothing. My gut is telling me that I should be using a different data type or a different filter option. Here is how my text type is defined: Thanks for your help.
