: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, Augu
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'
; 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@l
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
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 qu
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.
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-havin
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 anal
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
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 mapp
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
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 th
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.
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 l
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 would
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
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
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
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-character
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 searc
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
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.
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 th
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 wit
24 matches
Mail list logo
