> Best,
> Erick
>
> On Sat, Mar 30, 2019, 10:33 ahemad.sh...@yahoo.com.INVALID
> wrote:
>
>> Hi ,
>> I have field with white spaces and special characters on which indexing
>> needs to be done to do wildcard querying.
>> It works for most of the scnearios wi
t; needs to be done to do wildcard querying.
> It works for most of the scnearios with wildcard search.
> e.g. if my data is "ali.abc" and "abc_pqr" and "ali abc" and "ahemad ali"
> then search with ali* gives this three results.
>
> But I
Hi ,
> I have field with white spaces and special characters on which indexing
> needs to be done to do wildcard querying.
> It works for most of the scnearios with wildcard search.
> e.g. if my data is "ali.abc" and "abc_pqr" and "ali abc" and "ahemad ali
Hi ,
I have field with white spaces and special characters on which indexing needs
to be done to do wildcard querying.
It works for most of the scnearios with wildcard search.
e.g. if my data is "ali.abc" and "abc_pqr" and "ali abc" and "ahemad ali" then
s
rote:
>
> > Am 22.12.2017 um 11:57 schrieb Selvam Raman:
> > > 1) how can i disable leading wildcard search
> >
> > Do it on the client side. Just don't allow leading asterisks or question
> > marks in your query term.
> >
> > > 2) why lea
; 1) how can i disable leading wildcard search
>
> Do it on the client side. Just don't allow leading asterisks or question
> marks in your query term.
>
> > 2) why leading wildcard search takes so much of time to give the
> response.
> >
>
> Because Lucene can'
t; have
> > > the following settings:
> > >
> > > schema.xml - https://pastebin.com/1XXWTs8V
> > > solrconfig.xml - https://pastebin.com/5HSswCcv
> > >
> > > But under these settings, the search works only on the full
> coincidence,
> > >
Hi Rick!
Yes, as soon as I get the required result I'll definitely publish it on
GitHub. Dovecot default scheme doesn't suit me, when I use it the search
works according to the full word, but I want to make it wildcard search. I
don't have the solution. Hope the this group will hel
t;
>> But under these settings, the search works only on the full
>coincidence,
>> for instance, if I search for Chris it doesn't find Christmas. The
>client
>> does not support wildcard search. I would like to know how to turn on
>> wildcard search for all que
erver (dovecot 2.32). I
> have
> > the following settings:
> >
> > schema.xml - https://pastebin.com/1XXWTs8V
> > solrconfig.xml - https://pastebin.com/5HSswCcv
> >
> > But under these settings, the search works only on the full coincidence,
> > for instance, if I
find Christmas. The client
> does not support wildcard search. I would like to know how to turn on
> wildcard search for all queries.
>
> I tried to do that by adding the following line to schema.xml
>
>
>
> but when I added it, Solr 6.6.1 very often showed errors during the
config.xml - https://pastebin.com/5HSswCcv
>
> But under these settings, the search works only on the full coincidence,
> for instance, if I search for Chris it doesn't find Christmas. The client
> does not support wildcard search. I would like to know how to turn on
> wildcard search f
search for Chris it doesn't find Christmas. The client
does not support wildcard search. I would like to know how to turn on
wildcard search for all queries.
I tried to do that by adding the following line to schema.xml
but when I added it, Solr 6.6.1 very often showed errors durin
Am 22.12.2017 um 11:57 schrieb Selvam Raman:
> 1) how can i disable leading wildcard search
Do it on the client side. Just don't allow leading asterisks or question
marks in your query term.
> 2) why leading wildcard search takes so much of time to give the response.
>
Becaus
Hi,
Solr version - 6.4
Parser - Edismax
Leading wildcard search is allowed in edismax.
1) how can i disable leading wildcard search
2) why leading wildcard search takes so much of time to give the response.
--
Selvam Raman
"லஞ்சம் தவிர்த்து நெஞ்சம் நிமிர்த்து"
AFAICT The behavior you're describing with Trie fields was never
intentionally supported/documented?
It appears that it only worked as a fluke side effect of how the default
implementation of FieldType.getprefixQuery() was inherited by Trie fields
*and* because "indexed=true" TrieFields use T
Hi,
some question about the new DoublePointField which should be used
instead of the TrieDoubleField in 7.1.
https://lucene.apache.org/solr/guide/7_1/field-types-included-with-solr.html
If i am using the deprecated one its possible to get a match for a
double field like this:
test_d:*
even in
solr-user@lucene.apache.org
Subject: RE: Solr Wildcard Search
At the very least the English possessive filter, which you have. Great!
Depending on what your query log analysis finds -- perhaps users are pretty
much only searching on nouns? -- you might consider
EnglishMinimalStemFilterFactory.
ircumstances. Good luck finding the name "newing".
-Original Message-
From: Georgy Nevsky [mailto:gnevsky.cn...@thomasnet.com]
Sent: Thursday, November 30, 2017 8:31 AM
To: solr-user@lucene.apache.org
Subject: RE: Solr Wildcard Search
I understand stemming reason. Thank you.
Wha
vember 30, 2017 8:25 AM
To: solr-user@lucene.apache.org
Subject: RE: Solr Wildcard Search
The initial question wasn't about a phrasal search, but I largely agree that
diff q parsers handle the analysis chain differently for multiterms.
Yes, Porter is crazily aggressive. USE WITH CAUTION!
As
27;t find it. It would find "shippqrs"
because porter wouldn't know what to do with that 😊
Again, Porter can be very dangerous if it doesn't align with user expectations.
-Original Message-
From: Atita Arora [mailto:atitaar...@gmail.com]
Sent: Thursday, November 3
As Rick raised the most important aspect here , that the phrase is broken
into multiple terms ORed together ,
I believe if the use case requires to perform wildcard search on phrases ,
we would need to store the entire phrase as a single term in the index
which probably is not happening right now
ache Solr 7.1.0.
In the best we trust
Georgy Nevsky
-Original Message-
From: Rick Leir [mailto:rl...@leirtech.com]
Sent: Thursday, November 30, 2017 7:32 AM
To: solr-user@lucene.apache.org
Subject: Re: Solr Wildcard Search
George,
When you get those results it could be due to stemming.
e the analysis
tab to understand what is going on.
If you still have doubts, tell us more about your config.
Cheers --Rick
On November 30, 2017 7:06:42 AM EST, Georgy Nevsky
wrote:
>Can somebody help me understand how Solr Wildcard Search is working?
>
>If I’m doing search for “s
Can somebody help me understand how Solr Wildcard Search is working?
If I’m doing search for “ship*” term I’m getting in result many strings,
like “Shipping Weight”, “Ship From”, “Shipping Calculator”, etc.
But if I’m searching for “shipp*” I don’t get any result.
In the best we trust
Georgy
Hi,
I think AutomatonQuery is used.
http://opensourceconnections.com/blog/2013/02/21/lucene-4-finite-state-automaton-in-10-minutes-intro-tutorial/
https://lucene.apache.org/core/5_4_0/core/org/apache/lucene/search/AutomatonQuery.html
Ahmet
On Thursday, September 8, 2016 3:54 PM, Sandeep Khanzo
Hi,
Okay.
So it seems that the wildcard searches will perform a (sort-of) dictionary
search where they will inspect every (full keyword) token at search time, and
do a match instead of a match on pre-created index-time tokens with TextField.
However, the wildcard/fuzzy functionality will still b
Hi,
EdgeNGram and Wildcard may be used to achieve the same goal: prefix search or
starts with search.
Lets say, wildcard enumerates the whole inverted index, thus it may get slower
for very large databases.
With this one no index time manipulation is required.
EdgeNGram does its magic at index
Hello,
There are quite a few links that detail the difference between StrField and
TextField. Also links that explain that, even though the field is indexed, it
is not tokenized and stored as a single keyword, as can be verified by the
debug analysis on Solr admin and CURL debugQuery options.
Wh
: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
, 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
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 matche
Great.
First option worked for me. I was trying with q=abc\sp*... it should be q=abc\
p*
Thanks
-Original Message-
From: Ahmet Arslan [mailto:iori...@yahoo.com]
Sent: Wednesday, June 15, 2016 6:25 PM
To: solr-user@lucene.apache.org; Roshan Kamble
Subject: Re: wildcard search for string
I am using above field to ensure that entire string is considered as single
token and search should be case insensitive.
It works for most of the scnearios with wildcard search.
e.g. if my data is "abc.pqr" and "abc_pqr" and "abc pqr" then sear
Hello,
I have below custom field type defined for solr 6.0.0
I am using above field to ensure that entire string is considered as single
token and search should be case insensitive.
It works for most of the scnearios with wildcard search
igure out why various queries don't work as expected.
How big is your corpus - number of documents and average document size?
-- Jack Krupansky
On Sat, Jun 27, 2015 at 6:27 AM, octopus wrote:
> Hi, I'm looking at Solr's features for wildcard search used for a large
> amount
M, octopus wrote:
>> Hi, I'm looking at Solr's features for wildcard search used for a large
>> amount of text. I read on the net that solr.EdgeNGramFilterFactory is used
>> to generate tokens for wildcard searching.
>>
>> For Nigerian => "ni", "
On 6/27/2015 4:27 AM, octopus wrote:
> Hi, I'm looking at Solr's features for wildcard search used for a large
> amount of text. I read on the net that solr.EdgeNGramFilterFactory is used
> to generate tokens for wildcard searching.
>
> For Nigerian => "ni&
Hi, I'm looking at Solr's features for wildcard search used for a large
> amount of text. I read on the net that solr.EdgeNGramFilterFactory is
> used
> to generate tokens for wildcard searching.
>
> For Nigerian => "ni", "nig", "nige", "
Hi, I'm looking at Solr's features for wildcard search used for a large
amount of text. I read on the net that solr.EdgeNGramFilterFactory is used
to generate tokens for wildcard searching.
For Nigerian => "ni", "nig", "nige", "niger", "
Awesome thanks! I was on 4.10.2
Ryan
> On Apr 22, 2015, at 16:44, Joel Bernstein wrote:
>
> For your own implementation you'll need to implement the following methods:
>
> public Query rewrite(IndexReader reader) throws IOException
> public void extractTerms(Set terms)
>
> You can review the
For your own implementation you'll need to implement the following methods:
public Query rewrite(IndexReader reader) throws IOException
public void extractTerms(Set terms)
You can review the 4.10.3 version of the ReRankQParserPlugin to see how it
implements these methods.
Joel Bernstein
http://j
Just confirmed that wildcard queries work with Re-Ranking following
SOLR-6323.
Joel Bernstein
http://joelsolr.blogspot.com/
On Wed, Apr 22, 2015 at 7:26 PM, Joel Bernstein wrote:
> This should be resolved in https://issues.apache.org/jira/browse/SOLR-6323
> .
>
> Solr 4.10.3
>
> Joel Bernstein
This should be resolved in https://issues.apache.org/jira/browse/SOLR-6323.
Solr 4.10.3
Joel Bernstein
http://joelsolr.blogspot.com/
On Wed, Apr 15, 2015 at 6:23 PM, Ryan Josal wrote:
> Using edismax, supplying a rq= param, like {!rerank ...} is causing an
> UnsupportedOperationException becau
Using edismax, supplying a rq= param, like {!rerank ...} is causing an
UnsupportedOperationException because the Query doesn't implement
createWeight. This is for WildcardQuery in particular. From some
preliminary debugging it looks like without rq, somehow the qf Queries
might turn into Constant
Thank you very much,
this information is worht it's weight in gold. So far, we've used the
asterisk method because it seemed logical and straight-forward. We will
slowly migrate to a version using EdgeNGramFilterFactory.
Thanks a bunch.
Am 07.10.2014 14:42 schrieb Alexandre Rafalovitch:
On
Hi - you should not use wild cards for autocompletion, Lucene has far better
tools for making very good autocompletion, also, since a wild card is a multi
term query, they are not passed through your configured query time analyzer.
Some other comments:
- you use a porter stemmer but you should u
On 7 October 2014 08:25, Thomas Michael Engelke
wrote:
> So the culprit is the asterisk at the end. As far as we can read from the
> docs, an asterisk is just 0 or more characters, which means that the literal
> word in front of the asterisk should match the query.
Not quite: http://wiki.apache.o
I have a problem with a stemmed german field. The field definition:
stored="true" required="false" multiValued="false"/>
...
positionIncrementGap="100" autoGeneratePhraseQueries="true">
words="stopwords.txt"/>
generateWordParts="1" generateNumberParts="1" catenateWords="1"
catenateN
an be searched for individually. The tokenizer
> does the initial job of separating the input into tokens (terms) ...
> some filters can create additional terms, depending on exactly what's
> left when the tokenizer is done.
>
> Thanks,
> Shawn
>
>
>
> --
right, prior to 3.6, the standard way to handle wildcards was to,
essentially, pre-analyze the terms that had wildcards. This works
fine for simple filters, things like lowercasing for instance, but
doesn't work so well for things like stemming.
So you're doing what can be done at this point, but
On 10/2/2014 4:33 AM, waynemailinglist wrote:
> Something that is still not clear in my mind is how this tokenising works.
> For example with the filters I have when I run the analyser I get:
> Field: Hello You
>
> Hello|You
> Hello|You
> Hello|You
> hello|you
> hello|you
>
>
> Does this mean th
x27; (the final one) and
that when I run a query and it goes through the filters whatever the end
result of that is must match the 'hello|you' in order to return a result?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Wildcard-search-makes-no-sense-tp4162069p4
generateNumberParts="1" catenateWords="0" catenateNumbers="0"
> catenateAll="0"/>
>
>
>
>
> I tried adding ASCIIFoldingFilterFactory but that didm;t make any difference
> after reindexing.
>
> Any ideas?
>
> many thanks
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Wildcard-search-makes-no-sense-tp4162069p4162150.html
> Sent from the Solr - User mailing list archive at Nabble.com.
used in query)
> words="stopwords.txt"/>
> generateNumberParts="1" catenateWords="0" catenateNumbers="0"
> catenateAll="0"/>
>
>
>
>
> I tried adding ASCIIFoldingFilterFactory but that didm;t make any difference
> after reindexing.
>
> Any ideas?
>
> many thanks
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Wildcard-search-makes-no-sense-tp4162069p4162150.html
> Sent from the Solr - User mailing list archive at Nabble.com.
ce
after reindexing.
Any ideas?
many thanks
--
View this message in context:
http://lucene.472066.n3.nabble.com/Wildcard-search-makes-no-sense-tp4162069p4162150.html
Sent from the Solr - User mailing list archive at Nabble.com.
Ahmet - many thanks - I removed the EnglishPorterFilterFactory and reindexed
and this seems to behave as expected now.
Jack - thanks aswell - I'm very much a noob with this, and thats a great
tip.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Wildcard-search-mak
token gets analyzed into - that's what your wildcard prefix must
match. Sometimes (usually!) you will be surprised.
-- Jack Krupansky
-Original Message-
From: Wayne W
Sent: Wednesday, October 1, 2014 7:16 AM
To: solr-user@lucene.apache.org
Subject: Wildcard search makes no sense!
On Wed, 2014-10-01 at 13:16 +0200, Wayne W wrote:
> query 2: capit*
> result: Capital Health
>
> query 3: capita*
> result:
You are likely using a stemmer for the field: "Capital Health" gets
indexed as "capit" and "health", so there are no tokens starting with
"capita".
Turn off the stemmer or
names. When we
do a standard query:
query 1: capi*
result: Capital Health
query 2: capit*
result: Capital Health
query 3: capita*
result:
query 4: capital*
result:
I understand (as we are using solar 3.5) that the wildcard search does not
actually return the query without the wildcard
Hi,
I don't understand this at all. We are indexing some contact names. When we
do a standard query:
query 1: capi*
result: Capital Health
query 2: capit*
result: Capital Health
query 3: capita*
result:
query 4: capital*
result:
I understand (as we are using solar 3.5) that the wil
alhost:8080/solr/master/select?q=page_title_t:*products*
> http://localhost:8080/solr/master/select?q=page_title_t:*product*
>
>
> Please let me know if I am doing anything wrong.
>
> Thanks,
> G. Naresh Kumar
>
>
>
> --
> View this message in context:
> http:
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.
Can someone help me out with this issue?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Stemming-not-working-with-wildcard-search-tp4133382p4133769.html
Sent from the Solr - User mailing list archive at Nabble.com.
://localhost:8080/solr/master/select?q=page_title_t:*product*
Please let me know if I am doing anything wrong.
Thanks,
G. Naresh Kumar
--
View this message in context:
http://lucene.472066.n3.nabble.com/Stemming-not-working-with-wildcard-search-tp4133382p4133556.html
Sent from the Solr - User mailing
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
ansky
-Original Message-
From: Geepalem
Sent: Sunday, April 27, 2014 3:13 PM
To: solr-user@lucene.apache.org
Subject: Stemming not working with wildcard search
Hi,
I have added SnowballPorterFilterFactory filter to field type to make
singular and plural search terms return same results.
So
-Original Message-
From: Geepalem
Sent: Sunday, April 27, 2014 3:13 PM
To: solr-user@lucene.apache.org
Subject: Stemming not working with wildcard search
Hi,
I have added SnowballPorterFilterFactory filter to field type to make
singular and plural search terms return same results.
So
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&q
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
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/Stemming-not-working-with-wildcard-search-tp4133382p4133477.html
Sent from the Solr - User mailing list archive at Nabble.com.
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 wi
prefix and suffix to search term without double quotes
to do wildcard search.
http://localhost:8080/solr/master/select?q=page_title_t:*product*
http://localhost:8080/solr/master/select?q=page_title_t:*products*
Now, stemming is not working as above second query is not returning similar
results as que
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.
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.htm
erested 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-conati
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.
sterisk. 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-tp41196
s 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.
>
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
%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.
stopwords.txt" enablePositionIncrements="true" />
>
>
>
>
>
> words="stopwords.txt" enablePositionIncrements="true" />
>
>
>
>
>
>
> Please help we with this.
>
> Th
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-spec
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-alo
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-worki
: Prasi S
> Sent: Friday, September 13, 2013 6:37 AM
> To: solr-user@lucene.apache.org
> Subject: Solr wildcard search
>
>
> Hi all,
> I am working with wildcard queries and few things are confusing.
>
> 1. Does a wildcard search omit the analysers on a particular field
Hi all,
I am working with wildcard queries and few things are confusing.
1. Does a wildcard search omit the analysers on a particular field?
2. I have searched for
q=google\ technology - >gives result
q=google technology -> Gives results
q=google tech* -> gives results
q=google\ t
@lucene.apache.org
Subject: Solr wildcard search
Hi all,
I am working with wildcard queries and few things are confusing.
1. Does a wildcard search omit the analysers on a particular field?
2. I have searched for
q=google\ technology - >gives result
q=google technology -> Gives results
q=googl
is to preprocess your queries in your application layer and
perform the mapping there.
-- Jack Krupansky
-Original Message-
From: Sandeep Gupta
Sent: Tuesday, July 30, 2013 5:22 AM
To: solr-user@lucene.apache.org
Subject: Synonyms with wildcard search
Hello All,
I want to know whether
Hello All,
I want to know whether it is possible to make a query of word which has
synonym+wildcard.
For example : I have one field which is type of text_en (default fieldType
in 4.3.1)
And synonym.txt file has this entry
colour => color
Now when I am using full text search as colour* (with wil
François Schiettecatte
> Sent: Monday, November 12, 2012 2:38 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Is leading wildcard search turned on by default in Solr 3.6.1?
>
>
> John
>
> You can still use leading wildcards even if you dont have the
> ReversedWildcar
.
Technology advances. We should permit our mindsets to advance as well.
-- Jack Krupansky
-Original Message-
From: François Schiettecatte
Sent: Monday, November 12, 2012 2:38 PM
To: solr-user@lucene.apache.org
Subject: Re: Is leading wildcard search turned on by default in Solr 3.6.1?
John
You
On Tue, Nov 13, 2012 at 2:27 AM, wrote:
> I'm surprised that this has not been logged as adefect. The fact that this
> is ON bydefault, means someone can bring down a server; this is bad enough to
> categorizethis as a security issue.
It's all relative. There are tons of queries that can tak
onday, November 12, 2012 8:10 PM
To: solr-user@lucene.apache.org
Subject: RE: Is leading wildcard search turned on by default in Solr 3.6.1?
Yeah, thesituation is kind of a pain right now. In
https://issues.apache.org/jira/browse/SOLR-2438, it was enabled by default and
there is noway to disable wi
Sent: Monday, November 12, 2012 7:58 PM
To: solr-user@lucene.apache.org
Subject: RE: Is leading wildcard search turned on by default in Solr 3.6.1?
At one point, in some version of Solr, it was OFF by default, and you had to
enable it via a setting (either in solrconfig.xml or schema.xml, I don
sable it via a Solr
setting!!
-- MJ
-Original Message-
From: François Schiettecatte [mailto:fschietteca...@gmail.com]
Sent: Monday, November 12, 2012 7:48 PM
To: solr-user@lucene.apache.org
Subject: Re: Is leading wildcard search turned on by default in Solr 3.6.1?
I suspect it is just
> Sent: Mon, Nov 12, 2012 5:39 pm
> Subject: Re: Is leading wildcard search turned on by default in Solr 3.6.1?
>
>
> John
>
> You can still use leading wildcards even if you dont have the
> ReversedWildcardFilterFactory in your analysis but it means you will be
&
1 - 100 of 228 matches
Mail list logo
