https://lucene.apache.org/solr/4_6_0/solr-core/org/apache/solr/analysis/ReversedWildcardFilterFactory.html
?
On Tue, Jan 19, 2021 at 4:01 AM mosheB wrote:
>
> Hi, is there any sophisticated way [using the schema] to block brutal regex
> queries?
>
>
> Thanks
>
>
>
> --
> Sent from: https://lucene
Hi, is there any sophisticated way [using the schema] to block brutal regex
queries?
Thanks
--
Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
d
[72 6f 64]
0
3
1
word
1
1
false
s
[73]
4
5
1
word
1
2
false
This is what we were trying to achieve with the class="solr.PatternReplaceFilterFactory" pattern="’" replacement="'"/>
The problem is when using wildcard *Rod’s* we get no h
Why do you say “…that are now in the index as rod’s”? You have
WordDelimiterGraphFilterFactory, which breaks things up. When I put your field
definition in the schema and use the analysis page, turns “rod’s” into the
following 4 tokens:
rod’s
rods
rod
s
And querying on field:”*Rod’s*” works j
Is this a bug? Wildcard with PatternReplaceFilterFactory
Attempting to normalize left and right single and double quotes for searches
‘ Left single quotation mark ' Single quote
’ Right single quotation mark ' Single quote
“ Left double quot
On 2/3/2020 12:06 PM, Rahul Goswami wrote:
I am working with Solr 7.2.1 and had a question regarding the performance
of wildcard searches.
q=*:*
vs
q=id:*
vs
q=id:[* TO *]
Can someone please rank them in the order of performance with the
underlying reason?
The only one of those that is an
Hello,
I am working with Solr 7.2.1 and had a question regarding the performance
of wildcard searches.
q=*:*
vs
q=id:*
vs
q=id:[* TO *]
Can someone please rank them in the order of performance with the
underlying reason?
Thanks,
Rahul
I've got a collection for which the schema has
a number of copyFields that have a wildcard in the source:
The idea is that I have fields in each document
that contain language-specific values in
fields that have field names that end in a language tag,
i.e., "skos_pr
s the remaining non-ascii symbols.
However, it does cause odd behaviour in Wildcard Queries. e.g.:
The query title:todesmä* matches todesmarsch, which it should not, because
an ä is supposed to be replaced with an ae, however, it also matches
todesmärchen, as it should.
The query title:todesmär still ma
Hello,
I am having a bit of a problem with Wildcard queries and I don't know how
to pin it down yet. I have a suspect, but I kind find an error in it, one
of the filters in the respective search field.
The problem is that when I do a wildcard query:
title:todesmä*
it does return a result, b
> 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'
PM
To: solr-user@lucene.apache.org
Subject: RE: Add Wildcard Certificate to Java Keystore
Hi Chris,
All I have is the .p12 and password so it has already gone through the CSR
process. How do I import this file into the keystore? On the Windows side, does
it need to reside in the Personal Store
Hi Chris,
Thanks for the assistance. It is from a real CA. I was sent the .p12 Wildcard
certificate and I need to use that to HTTPS my Solr address.
Kelly
-Original Message-
From: Christopher Schultz
Sent: Monday, August 13, 2018 12:59 PM
To: solr-user@lucene.apache.org
Subject: Re
M To: solr-user@lucene.apache.org Subject: Re: Add Wildcard
> Certificate to Java Keystore
>
> Kelly,
>
> On 8/13/18 11:55 AM, Kelly Rusk wrote:
>> I have imported a Wildcard Certificate to my Java Keystore and it
>> displays, but when I pull up Internet Explorer and
Sent: Monday, August 13, 2018 12:00 PM
To: solr-user@lucene.apache.org
Subject: Re: Add Wildcard Certificate to Java Keystore
Kelly,
On 8/13/18 11:55 AM, Kelly Rusk wrote:
> I have imported a Wildcard Certificate to my Java Keystore and it
> displays, but when I pull up Internet Explorer and
Kelly,
On 8/13/18 11:55 AM, Kelly Rusk wrote:
> I have imported a Wildcard Certificate to my Java Keystore and it
> displays, but when I pull up Internet Explorer and browse to my Solr
> site, it fails to load and presents TLS errors.
What do you mean "it displays"?
How
Hi all,
I have imported a Wildcard Certificate to my Java Keystore and it displays, but
when I pull up Internet Explorer and browse to my Solr site, it fails to load
and presents TLS errors.
Has anyone run into this, what commands do you run to import a Public CA into
Solr?
Regards,
Kelly
comes with solr 7.2.1):
> ---8<
> positionIncrementGap="100">
>
>
> words="stopwords.txt" />
>
>
>
>
>
> words="stopwords.txt" />
> sy
#x27; (numeric).
Searching without wildcard also returns zero results...
As I mentioned before: we are testing this all, so we are not really up to
speed with the why-does-this-do-that, although I am trying to learn.
Thanks for any other pointers you can provide.
Greetings,
Roel
-Origina
in UI>>analysis
page (probably uncheck the "verbose" checkbox, there'll be less
clutter").
Best,
Erick
On Fri, Mar 16, 2018 at 8:35 AM, Emir Arnautović
wrote:
> Hi Roel,
> As mentioned, _text_ field probably does not contain complete “EO.1954.53.1”
> but only
Hi Roel,
As mentioned, _text_ field probably does not contain complete “EO.1954.53.1”
but only its parts. You can verify that using snalysis screen in admin console.
What you can try is searching for phrase without wildcard “EO.1954.53” or if
you are using WordDelimiterTokenFilter in your
[mailto:jagdisht.vas...@gmail.com]
Sent: vrijdag 16 maart 2018 12:41
To: solr-user@lucene.apache.org
Subject: Re: question regarding wildcard-searches
Hi paesen,
Value - EO.1954.53.1 is indexed as below Eo
1954
53
1
Dot is removed.try with wildcard -?
Like EO.1954.53.?? If you have 2 digits only in last..
I have
Hi paesen,
Value - EO.1954.53.1 is indexed as below
Eo
1954
53
1
Dot is removed.try with wildcard -?
Like EO.1954.53.?? If you have 2 digits only in last..
I have not tried but you just check it.
Hope it will solve your problem.
Thanks,
Jagdish
On 16-Mar-2018 3:51 pm, "Paesen Roel&qu
Hi everybody,
We are experimenting with solr, and I have a (I think) basic-level question:
we have a multiple fields, all copied into a generic field so we can search
everything at once.
However we have a (for us) strange situation doing wildcard searches for the
contents of one specific field
uh...oops - sorry about that
Sent via the Samsung Galaxy S® 6, an AT&T 4G LTE smartphone
Original message
From: David M Giannone
Date: 1/25/18 8:28 PM (GMT-05:00)
To: solr-user@lucene.apache.org
Subject: Re: [EXTERNAL] Highlighter is not working for wildcard q
X07Z3BO14C
confirmation# for 1/30 8:30 appt. oil change / tire rotation
Sent via the Samsung Galaxy S® 6, an AT&T 4G LTE smartphone
Nothing in this message is intended to constitute an electronic signature
unless a specific statement to the contrary is included in this message.
Confidentiali
ucene.apache.org
> Subject: [EXTERNAL] Highlighter is not working for wildcard query
>
> Hi,
>
> solr version 6.4.2
>
> hl.method = unified, hl.bs.type=Word, this setting working fine for normal
> queries but failed in wildcard queries.(tried other hl.bs.type parmeter a
Sent via the Samsung Galaxy S® 6, an AT&T 4G LTE smartphone
Original message
From: Selvam Raman
Date: 1/17/18 11:47 AM (GMT-05:00)
To: solr-user@lucene.apache.org
Subject: [EXTERNAL] Highlighter is not working for wildcard query
Hi,
solr version 6.4.2
hl.me
Query Parser
defType=edismax
On Wed, Jan 17, 2018 at 4:47 PM, Selvam Raman wrote:
> Hi,
>
> solr version 6.4.2
>
> hl.method = unified, hl.bs.type=Word, this setting working fine for normal
> queries but failed in wildcard queries.(tried other hl.bs.type parm
Hi,
solr version 6.4.2
hl.method = unified, hl.bs.type=Word, this setting working fine for normal
queries but failed in wildcard queries.(tried other hl.bs.type parmeter and
without hl.bs.type as well, highlighting not working for wildcard queries)
hl.method = original, this is working fine for
gt; You can start to explore different aspects of this field from
> > https://lucidworks.com/2015/03/04/solr-suggester/
> > You see NGamming just freak the heap out. So, you can band aid it with
> > EdgeNGram (and it's what you probably want to have) and add some heap to
&g
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
d it with
> EdgeNGram (and it's what you probably want to have) and add some heap to
> your poor server.
> Another approach, is to stop ngramming but try to really search by wildcard
> with http://yonik.com/solr-query-parameter-substitution/
> It should be something like q=${text}*
ester/
You see NGamming just freak the heap out. So, you can band aid it with
EdgeNGram (and it's what you probably want to have) and add some heap to
your poor server.
Another approach, is to stop ngramming but try to really search by wildcard
with http://yonik.com/solr-query-parameter-substi
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
"லஞ்சம் தவிர்த்து நெஞ்சம் நிமிர்த்து"
Solr does not analyze queries with wildcards in it. So, with ch*p-seq,
it will search for terms that start with ch and end with p-seq. Since
your indexer has analyzed all tokens before, only chip and seq are in
the index.
See
https://solr.pl/en/2010/12/20/wildcard-queries-and-how-solr-handles
case one result.
>
> But when i am searching with wildcard it produce zero result.
> 1) ch*p-seq
>
>
> if i use escape character in '-' it creates two terms rather than single
> term.
>
> --
> Selvam Raman
> "லஞ்சம் தவிர்த்து நெஞ்சம் நிமிர்த்து"
>
--
Selvam Raman
"லஞ்சம் தவிர்த்து நெஞ்சம் நிமிர்த்து"
Solr version - 6.4.0
"title_en":["Chip-seq"]
When i fired query like below
1) chip-seq
2) chi*
it is giving expected result, for this case one result.
But when i am searching with wildcard it produce zero result.
1) ch*p-seq
if i use escape character in '-' it
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
es work. Porter doesn't have rules
for words ending in "pp", so it doesn't stem "shipp" to "ship". So, your
wildcard query is looking for words that start with "shipp", and given that
"shipping" was stemmed to "ship", it won&#x
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.
George,
When you get those results it could be due to stemming.
Wildcard processing expands your term to multiple terms, OR'd together. It also
takes you down a different analysis pathway, as many analysis components do not
work with multiple terms. Look into the SolrAdmin console, and us
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 Sundeep,
The simplified explanation is that terms are indexed to be more prefix search
friendly (and that is why Amrit suggested that you index term reversed if you
want leading wildcard). If you use leading wildcard, there is no structure to
limit terms that can be matched and engine has to
ch is not tokenized and does not
> have docValues enabled.
>
> When we do leading wildcard searches on these fields they are running very
> slow. We were thinking that since this field is indexed, such queries
> should be running pretty quickly. We are using Solr 6.6.1. Anyone ha
Hi,
We have several indexed string fields which is not tokenized and does not
have docValues enabled.
When we do leading wildcard searches on these fields they are running very
slow. We were thinking that since this field is indexed, such queries
should be running pretty quickly. We are using
ig just in case).
From: solr-user@lucene.apache.org At: 09/21/17 13:28:13To:
solr-user@lucene.apache.org
Subject: Re: Is there a way to delete multiple documents using wildcard?
Hi,
Delete by query should work - posting to /update
*:*
should delete all doc.
HTH,
Emir
> On 21 Sep 2
Hi,
Delete by query should work - posting to /update
*:*
should delete all doc.
HTH,
Emir
> On 21 Sep 2017, at 05:25, balmydrizzle wrote:
>
> Doesn't work, either. wildcard query can't be used in delete. At least for
> old Solr 3.x
>
>
>
> --
&g
Doesn't work, either. wildcard query can't be used in delete. At least for
old Solr 3.x
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
ame score 1.0, so maybe not a solution?
>
> Bernd
>
>>
>> On Tue, Jul 25, 2017 at 3:39 PM, Bernd Fehling <
>> bernd.fehl...@uni-bielefeld.de> wrote:
>>
>>> Any wildcard query will do it, e.g. .../select?q=ant*&wt=json&...
>>>
>>&g
Bernd
>
> On Tue, Jul 25, 2017 at 3:39 PM, Bernd Fehling <
> bernd.fehl...@uni-bielefeld.de> wrote:
>
>> Any wildcard query will do it, e.g. .../select?q=ant*&wt=json&...
>>
>> A couple of "shift + reload" (to bypass cache) in the browser and yo
Since all scores are equal it just can not break this tie. Add id as a sort
clause to make results deterministic.
On Tue, Jul 25, 2017 at 3:39 PM, Bernd Fehling <
bernd.fehl...@uni-bielefeld.de> wrote:
> Any wildcard query will do it, e.g. .../select?q=ant*&wt=json&...
>
i thought you said different results i.e. different count.
On Tue, Jul 25, 2017 at 8:39 AM, Bernd Fehling <
bernd.fehl...@uni-bielefeld.de> wrote:
> Any wildcard query will do it, e.g. .../select?q=ant*&wt=json&...
>
> A couple of "shift + reload" (to bypass cac
Any wildcard query will do it, e.g. .../select?q=ant*&wt=json&...
A couple of "shift + reload" (to bypass cache) in the browser and you
will see that the order of the result changes sometimes.
Definately no updates/ingestion because it's currently a
SolrCloud test system
er) and a wildcard query
> I get different results between the same query.
>
> I assume this is alltogether due to the distributed search and
> the response time of each server and the constant score of 1.0 ???
>
> Is there any config where I can set the shard order (shard_1...sha
With SolrCloud 6.4.2 (5 shards on 5 server) and a wildcard query
I get different results between the same query.
I assume this is alltogether due to the distributed search and
the response time of each server and the constant score of 1.0 ???
Is there any config where I can set the shard order
It's the same in both cases:
enumerate all terms that start with "a" and collect them into
(conceptually) a huge OR query and execute it. There's been some work
lately to avoid the TooManyBooleanClauses exception, but it's still
the case that every term starting with "a" has to be examined and
eith
I have a question in terms of how solr/lucene will lookup terms from
postings list for the below two queries:
1. a*
2. a*gh
My understanding is that for first, it will get all terms starting with 'a'
and issue query on those terms.
For second, it will again get all terms starting with 'a', then r
Have you looked at ComplexPhraseQueryParser? It adds some expense of
course. See SOLR-1604.
Best,
Erick
On Fri, Jun 23, 2017 at 1:06 PM, Michael Craven wrote:
> I apologize in advance if this is too off topic or basic. I am a web
> developer on a Drupal site tasked with trying to improve searc
Sure:
https://cwiki.apache.org/confluence/display/solr/Other+Parsers#OtherParsers-ComplexPhraseQueryParser
-Original message-
> From:Michael Craven
> Sent: Friday 23rd June 2017 22:06
> To: solr-user@lucene.apache.org
> Subject: Proximity searches with a wildcard
>
&
I apologize in advance if this is too off topic or basic. I am a web developer
on a Drupal site tasked with trying to improve searching capabilities for our
users. A product manager asked to me if proximity searches and wildcards worked
on our search form. I did some testing and found that, yes,
t;:[] }}
<
filter class="solr.TurkishLowerCaseFilterFactory"/> <
filter class="solr.TurkishLowerCaseFilterFactory"/>
On 25 March 2017 at 21:15, Mikhail Khludnev wrote:
> Hello
> It sounds similar to
> https://lucidworks.com/2011/11/29/whats
sedquery: "eoe:yasın*"
but
q={!complexphrase}eoe:"YASIN*"
parsedquery: "ComplexPhraseQuery("YASIN*")",
FWIW
Erick
On Sat, Mar 25, 2017 at 11:15 AM, Mikhail Khludnev wrote:
> Hello
> It sounds similar to
> https://lucidworks.com/2011/11/29/wha
Hello
It sounds similar to
https://lucidworks.com/2011/11/29/whats-with-lowercasing-wildcard-multiterm-queries-in-solr/
(yep, I see TurkishLowerCaseFilterFactory there)
What's your analyzer for this field? Does it work for plain wildcards
queries? I'm asking because CPQP adds an oddity
Hello,
I have a problem with ComplexPhrase and TurkishLowerCaseFilterFactory.
When I search like {!complexphrase}SContent_tinx:"6* YAŞINDA",
{!complexphrase}SContent_tinx:"6* yaşında", results is correct.
{ "responseHeader":{ "zkConnected":true, "status":0, "QTime":104, "params":{
"q":"{!complex
Hi,
how about q=code_text:bolt*&fq=code_text:bolt
Ahmet
On Thursday, March 2, 2017 4:41 PM, Сергей Твердохлеб
wrote:
Hi,
is there way to separate exact match from wildcard match in solr response?
e.g. there are two documents: {code_text:bolt} and {code_text:bolter}. When
I search
H,
Emir
On 02.03.2017 14:41, Сергей Твердохлеб wrote:
Hi,
is there way to separate exact match from wildcard match in solr response?
e.g. there are two documents: {code_text:bolt} and {code_text:bolter}.
When
I search for "bolt" I want to get both results, but somehow grouped
>
>> code_text_exact:bolt^1 OR code_text:bolt
>>
>> If you want to use wildcards, you can use similar approach:
>>
>> code_text:bolt^1 OR code_text:bolt*
>>
>> HTH,
>> Emir
>>
>>
>> On 02.03.2017 14:41, Сергей Твердохлеб
y to get different score for different matches:
>
> code_text_exact:bolt^1 OR code_text:bolt
>
> If you want to use wildcards, you can use similar approach:
>
> code_text:bolt^1 OR code_text:bolt*
>
> HTH,
> Emir
>
>
> On 02.03.2017 14:41, Сергей Твердохлеб wrote:
>
&
wrote:
Hi,
is there way to separate exact match from wildcard match in solr response?
e.g. there are two documents: {code_text:bolt} and {code_text:bolter}. When
I search for "bolt" I want to get both results, but somehow grouped, so I
can determine either it was found wit
Hi,
is there way to separate exact match from wildcard match in solr response?
e.g. there are two documents: {code_text:bolt} and {code_text:bolter}. When
I search for "bolt" I want to get both results, but somehow grouped, so I
can determine either it was found with exact or non-e
Hi,
You could try this:
drop wildcard stuff altogether:
1) Employ edgengramfilter at index time.
2) Use plain searches at query time.
Ahmet
On Friday, November 25, 2016 4:59 PM, Sandeep Khanzode
wrote:
Hi All,
Can someone please assist with this query?
My data consists of:
1.] John Doe
2
something in the syntax.
SRK
On Thursday, November 24, 2016 11:16 PM, Sandeep Khanzode
wrote:
Hi All, Erick,
Please suggest. Would like to use the ComplexPhraseQueryParser for searching
text (with wildcard) that may contain special characters.
For example ...John* should match John V
Hi All, Erick,
Please suggest. Would like to use the ComplexPhraseQueryParser for searching
text (with wildcard) that may contain special characters.
For example ...John* should match John V. DoeJohn* should match Johnson
SmithBruce-Willis* should match Bruce-WillisV.* should match John V. F
M, Sandeep Khanzode
wrote:
> Thanks, Erick.
>
> I am actually not trying to use the String field (prefer a TextField here).
> But, in my comparisons with TextField, it seems that something like phrase
> matching with whitespace and wildcard (like, 'my do*' or say, 'my d
QueryParser
>
> Best,
> Erick
>
> On Sat, Nov 12, 2016 at 9:39 AM, Sandeep Khanzode
> wrote:
> > Thanks, Erick.
> >
> > I am actually not trying to use the String field (prefer a TextField
> here).
> > But, in my comparisons with TextField, i
eryParser
Best,
Erick
On Sat, Nov 12, 2016 at 9:39 AM, Sandeep Khanzode
wrote:
> Thanks, Erick.
>
> I am actually not trying to use the String field (prefer a TextField here).
> But, in my comparisons with TextField, it seems that something like phrase
> matching with whitespace an
Thanks, Erick.
I am actually not trying to use the String field (prefer a TextField here).
But, in my comparisons with TextField, it seems that something like phrase
matching with whitespace and wildcard (like, 'my do*' or say, 'my dog*', or
say, 'my dog has*') c
lated) observation is if I have 'field:a\ b', then the
> parsedQuery is field:a field:b. Which does not match as expected (matches
> individually).
>
> Can you please provide an example that I can use in Solr Query dashboard?
> That will be helpful.
>
> I have also see
e
documents that should match.
Another (maybe unrelated) observation is if I have 'field:a\ b', then the
parsedQuery is field:a field:b. Which does not match as expected (matches
individually).
Can you please provide an example that I can use in Solr Query dashboard? That
will be h
You can escape the space with a backslash as 'a\ b*'
Best,
Erick
On Thu, Nov 10, 2016 at 2:37 PM, Reth RM wrote:
> I don't think you can do wildcard on StrField. For text field, if your
> query is "category:(test m*)" the parsed query will be "category:
I don't think you can do wildcard on StrField. For text field, if your
query is "category:(test m*)" the parsed query will be "category:test OR
category:m*"
You can add q.op=AND to make an AND between those terms.
For phrase type wild card query su
Hi,
How does a search like abc* work in StrField. Since the entire thing is stored
as a single token, is it a type of a trie structure that allows such wildcard
matching?
How can searches with space like 'a b*' be executed for text fields (tokenized
on whitespace)? If we specify th
Khanzode
wrote:
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
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
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
1 - 100 of 944 matches
Mail list logo
