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.
Hi All,
Can someone please assist with this query?
My data consists of:
1.] John Doe
2.] John V. Doe
3.] Johnson Doe
4.] Johnson V. Doe
5.] John Smith
6.] Johnson V. Smith
7.] Matt Doe
8.] Matt V. Doe
9.] Matt Doe
10.] Matthew V. Doe
11.] Matthew Smith
12.] Matthew V. Smith
Querying ...
(a) Mat
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. Doe
Hi,
This is the typical TextField with ...
SRK
On Thursday, November 24, 2016 1:38 AM, Reth RM
wrote:
what is the fieldType of those records?
On Tue, Nov 22, 2016 at 4:18 AM, Sandeep Khanzode
wrote:
Hi Erick,
I gave this a try.
These are my results. Th
what is the fieldType of those records?
On Tue, Nov 22, 2016 at 4:18 AM, Sandeep Khanzode <
sandeep_khanz...@yahoo.com.invalid> wrote:
> Hi Erick,
> I gave this a try.
> These are my results. There is a record with "John D. Smith", and another
> named "John Doe".
>
> 1.] {!complexphrase inOrder=t
Hi Erick,
I gave this a try.
These are my results. There is a record with "John D. Smith", and another named
"John Doe".
1.] {!complexphrase inOrder=true}name:"John D.*" ... does not fetch any
results.
2.] {!complexphrase inOrder=true}name:"John D*" ... fetches both results.
Second observ
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*') can only be accomplished with a st
You have to query text and string fields differently, that's just the
way it works. The problem is getting the query string through the
parser as a _single_ token or as multiple tokens.
Let's say you have a string field with the "a b" example. You have a
single token
a b that starts at offset 0.
Hi Erick, Reth,
The 'a\ b*' as well as the q.op=AND approach worked (successfully) only for
StrField for me.
Any attempt at creating a 'a\ b*' for a TextField does not match any documents.
The parsedQuery in debug mode does show 'field:a b*'. I am sure there are
documents that should match.
An
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:test OR
> category:m*"
> You can add q.o
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 support, as per docs, it
is ComplexPhraseQueryPars
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 this type of qu
12 matches
Mail list logo
