From: Singh, Divya
Sent: 04 July 2025 14:40
To: d...@lucene.apache.org
Cc: Birajdar, Sharad (DI SW PLM LCS APPS ALM R&D7)
Subject: FW: Challenges with Chinese Query Matching and Wildcard Search in
Lucene (StandardAnalyzer / CJKAnalyzer)
From: Thakare, Monika (ext) (DI SW PLM LCS APPS A
Hello, can someone review my patch?
https://issues.apache.org/jira/browse/LUCENE-7917
--
Regards, Yegor Dovganich
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h..
On Sun, Oct 16, 2016 at 8:54 PM, Trejkaz wrote:
> On Sat, Oct 15, 2016 at 1:21 AM, Rajnish Kamboj wrote:
>> Hi
>>
>> Performance of Prefix, Wildcard and Regex queries?
>> Does Lucene internally optimizes this (using rewrite or something else) or
>> I ha
On Sat, Oct 15, 2016 at 1:21 AM, Rajnish Kamboj wrote:
> Hi
>
> Performance of Prefix, Wildcard and Regex queries?
> Does Lucene internally optimizes this (using rewrite or something else) or
> I have to manually create specific queries depending on input pattern.
>
> Exa
Hi
Performance of Prefix, Wildcard and Regex queries?
Does Lucene internally optimizes this (using rewrite or something else) or
I have to manually create specific queries depending on input pattern.
Example
if input is 78* create Prefix query
if input is 87?98* create Wildcard query
if input is
, Jun 10, 2016 at 4:56 AM, Kim Tu Truong
wrote:
> Hi,
> I am a new user. I have already built a simple application to search with
> wildcard query. In Lucene wildcard search, a Lucene wildcard syntax is
> converted into an automaton but i do not know which algorithm is used to do
&g
Hi,
I am a new user. I have already built a simple application to search with
wildcard query. In Lucene wildcard search, a Lucene wildcard syntax is
converted into an automaton but i do not know which algorithm is used to do
this. Please enlighten me?
Thanks and Regards!
T.
java-user@lucene.apache.org
Hi,
I'm trying to use code from lucene-core for following use-case in my
project.
Given a big sorted list of string words (call it dictionary) and a
wildcard/regex pattern, return the list of index of words from dictionary
that matched the wildcard pattern.
He
Wildcard queries don't seem to be working for PointValues in Lucene 6.0 .
For example, "new WildcardQuery(new Term(some_LongPoint_field_name, "*")"
does not find anything. A similar query worked fine with LongFields though.
While PointValues javadocs say "are ind
.com]
> Sent: Sunday, November 29, 2015 12:18 PM
> To: java-user@lucene.apache.org
> Subject: Re: Wildcard Terms and total word or phrase count
>
> You didn't post your code that creates the index. Make sure you are using a
> tokenized TextField rather than a single-token Str
Sent: Sunday, November 29, 2015 12:18 PM
To: java-user@lucene.apache.org
Subject: Re: Wildcard Terms and total word or phrase count
You didn't post your code that creates the index. Make sure you are using a
tokenized TextField rather than a single-token StringField.
-- Jack Krupansky
On F
t Lucene project, my other search projects have used Solr.
> I would like to find the total number of WildCard terms in a set of
> documents with 0-N matches per document.
> I would prefer not have to open each document where a match is found. I
> need to be able to support wildcards
-Original Message-
From: Michael Wilkowski [mailto:m...@silenteight.com]
Sent: Sunday, November 29, 2015 3:38 AM
To: java-user@lucene.apache.org
Subject: Re: Wildcard Terms and total word or phrase count
It is because your index does not contain term quar* and this statistics
function is not
find the total number of WildCard terms in a set of
> documents with 0-N matches per document.
> I would prefer not have to open each document where a match is found. I
> need to be able to support wildcards but my requirements are somewhat
> flexible in about phrase search support.
Hi -
This is my first Lucene project, my other search projects have used Solr.
I would like to find the total number of WildCard terms in a set of documents
with 0-N matches per document.
I would prefer not have to open each document where a match is found. I need
to be able to support
Hi all,
I'm using Apache Lucene and currently trying to combine Fuzzy and Prefix
(or Wildcard) query to implement a kind of suggestion mechanism.
For example, if the query is "levy", a document containing "Levinshtein" should
also be returned.
As there seems no buil
Yes, that's fair. We can't expect every query the user types to be perfect if
they don't understand the query language.
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Friday, October 31, 2014 3:42 PM
To: java-user
Subject: Re: Negative W
if they put in this.
>
> Thanks!
>
> -Original Message-
> From: Erick Erickson [mailto:erickerick...@gmail.com]
> Sent: Friday, October 31, 2014 11:47 AM
> To: java-user
> Subject: Re: Negative Wildcard Queries
>
> Um not sure what that means. Are you looki
We have users inputing Lucene queries, so I was wondering what would happen if
they put in this.
Thanks!
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Friday, October 31, 2014 11:47 AM
To: java-user
Subject: Re: Negative Wildcard Queries
Um not
hat.
Best,
Erick
On Fri, Oct 31, 2014 at 10:17 AM, Prad Nelluru wrote:
> Thanks!
>
> Is it possible to say -"hello world"* ?
>
> -Original Message-
> From: Erick Erickson [mailto:erickerick...@gmail.com]
> Sent: Thursday, October 30, 2014 10:15 PM
> To: jav
Thanks!
Is it possible to say -"hello world"* ?
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Thursday, October 30, 2014 10:15 PM
To: java-user
Subject: Re: Negative Wildcard Queries
Actually, "hello world*" is possible with the Comp
Hi all,
>
> Is it possible to query Lucene with a negative wildcard query like: -hello*?
> I know wildcards aren't allowed inside phrase queries, so -"hello world*"
> isn't possible.
>
> Thanks,
> Prad
-
Hi all,
Is it possible to query Lucene with a negative wildcard query like: -hello*? I
know wildcards aren't allowed inside phrase queries, so -"hello world*" isn't
possible.
Thanks,
Prad
son
>> Sent: Thursday, August 28, 2014 11:52 PM
>> To: java-user
>> Subject: Re: indexing all suffixes to support leading wildcard?
>>
>>
>> The "usual" approach is to index to a second field but backwards.
>> See ReverseStringFilter... Then all
-- From: Erick Erickson
> Sent: Thursday, August 28, 2014 11:52 PM
> To: java-user
> Subject: Re: indexing all suffixes to support leading wildcard?
>
>
> The "usual" approach is to index to a second field but backwards.
> See ReverseStringFilter... Then all your
: java-user
Subject: Re: indexing all suffixes to support leading wildcard?
The "usual" approach is to index to a second field but backwards.
See ReverseStringFilter... Then all your leading wildcards
are really trailing wildcards in the reversed field.
Best,
Erick
On Thu, Aug 28,
some short fields (phone num, email) that I'd like to search using
> good old string matching. (The full query is a boolean "or" that also uses
> real text fields.) I see the warnings about wildcard queries that start
> with *, and I'm wondering... do you think it wou
Hi,
I've got some short fields (phone num, email) that I'd like to search using
good old string matching. (The full query is a boolean "or" that also uses
real text fields.) I see the warnings about wildcard queries that start
with *, and I'm wondering... do you think i
/houses?/
-- Jack Krupansky
-Original Message-
From: Uwe Schindler
Sent: Tuesday, March 25, 2014 11:34 AM
To: java-user@lucene.apache.org
Subject: RE: Lucene Wildcard for zero or one character
The default WildcardQuery only supports:
'*' (star) is the wildcard in Wildcar
The default WildcardQuery only supports:
'*' (star) is the wildcard in WildcardQuery for zero or more chars.
'?' is exactly one char
Zero or exatly one char can only be done with a RegexpQuery:
https://lucene.apache.org/core/4_7_0/core/org/apache/lucene/search/RegexpQu
Hello,
does Lucene provide a zero or one character wildcard (like ? in Perl RegEx)?
Example of what I mean:
"house%" finds "house" and "houses"
As far as I know in Lucene the ? wildcard is for exactly one character,
but I need a zero or one character wild
s.com]
Sent: Thursday, February 06, 2014 5:19 PM
To: java-user@lucene.apache.org
Subject: RE: Wildcard searches
Sorry, but I don't know what exactly you mean by compile from these locations.
Do you mean I could download and customize the code?
Regards,
Raghu
-Original Message-
Fro
-user@lucene.apache.org
Subject: RE: Wildcard searches
Sorry, you're right. I'm not sure that it analyzes multiterm components,
either. The Surround query parser also has similar limitations.
Best bet might be to compile:
https://issues.apache.org/jira/i#browse/LUCENE-5205 or
https://issues.
--Original Message-
From: raghavendra.k@barclays.com [mailto:raghavendra.k@barclays.com]
Sent: Thursday, February 06, 2014 11:49 AM
To: java-user@lucene.apache.org
Subject: RE: Wildcard searches
Thank you, Tim.
I have read that ComplexPhraseQueryParser has issues while searching in more
ComplexPhraseQueryParser that you may be aware of? I am looking for
some examples. Thanks!
Regards,
Raghu
-Original Message-
From: Allison, Timothy B. [mailto:talli...@mitre.org]
Sent: Thursday, February 06, 2014 8:02 AM
To: java-user@lucene.apache.org
Subject: RE: Wildcard searches
Ditto Jack on
Ditto Jack on ComplexPhraseQueryParser.
See also: https://issues.apache.org/jira/i#browse/LUCENE-5205
-Original Message-
From: Jack Krupansky [mailto:j...@basetechnology.com]
Sent: Wednesday, February 05, 2014 6:59 PM
To: java-user@lucene.apache.org
Subject: Re: Wildcard searches
Take
On 2/5/2014 6:30 PM, raghavendra.k@barclays.com wrote:
Hi,
Can Lucene support wildcard searches such as the ones shown below?
Indexed value is "XYZ CORPORATION LIMITED".
If you index the value as a single token (KeywordTokenizer), there is
nothing really special about the ex
: raghavendra.k@barclays.com
Sent: Wednesday, February 5, 2014 6:30 PM
To: java-user@lucene.apache.org
Subject: Wildcard searches
Hi,
Can Lucene support wildcard searches such as the ones shown below?
Indexed value is "XYZ CORPORATION LIMITED".
XYZ CORPORATION LIMI*
XYZ CORPORATION *MIT*
Hi,
Can Lucene support wildcard searches such as the ones shown below?
Indexed value is "XYZ CORPORATION LIMITED".
XYZ CORPORATION LIMI*
XYZ CORPORATION *MIT*
XYZ *PORAT* LIMI*
*YZ CORPO* LIMITE*
In other words, the flexibility for the user to provide a wild card at any
posi
-Original Message-
From: raghavendra.k@barclays.com
Sent: Monday, November 18, 2013 9:32 AM
To: java-user@lucene.apache.org
Subject: RE: How to perform Wildcard search when using WhitespaceAnalyzer?
Jack,
I am using WhitespaceAnalyzer while both indexing and searching the data. To
. Please let me know what you think.
Regards,
Raghu
-Original Message-
From: Jack Krupansky [mailto:j...@basetechnology.com]
Sent: Monday, November 18, 2013 12:00 AM
To: java-user@lucene.apache.org
Subject: Re: How to perform Wildcard search when using WhitespaceAnalyzer?
The presence of a
The presence of a wildcard character causes the query parser to completely
skip analysis for that term.
You, the writer of the query terms, need to manually simulate all the the
work that the analyzer does when a wildcard is present in a term.
What does your query actually look like, and
Hi All,
Sorry to repeat this question from my previous mail chain, but I am hoping the
modified subject will catch someone's attention - in case they are familiar
with this situation.
Could any one please suggest if it is possible to perform Leading and / or
trailing wildcard sea
You seem to be indexing paths delimited by backslash then saying a
search for Samples/* doesn't match anything. No surprises there, if
I've read your code correctly. Since you are creating wildcard
queries directly from Terms I don't think that lucene escaping is
relevant here, B
IndexReader indexReader = DirectoryReader.open(directory);
IndexSearcher indexSearcher = new IndexSearcher(indexReader);
// Create a wildcard query to get all file paths
// This query works fine and returns all the docs in index
Query query1 = new W
Seems to me that it should work. I suggest you show us a complete
self-contained example program that demonstrates the problem.
--
Ian.
On Mon, Oct 14, 2013 at 12:42 PM, nischal reddy
wrote:
> Hi Ian,
>
> Actually im able to do wildcard searches on all the fields except the
&g
Hi Ian,
Actually im able to do wildcard searches on all the fields except the
"filePath" field. I am able to do both the leading and trailing wildcard
searches on all the fields,
but when i do the wildcard search on filepath field it is somehow not
working, an eg file path would look
> I am using StandardAnalyzer for IndexWriter
>
> but since i am using a StringField the fields are not analyzed.
>
> After the files are indexed i checked it with Luke the path seems fine. And
> when i do wildcard searches with luke i am getting desired results.
>
> But whe
LE_PATH,resourcePath, Store.YES));
I am using StandardAnalyzer for IndexWriter
but since i am using a StringField the fields are not analyzed.
After the files are indexed i checked it with Luke the path seems fine. And
when i do wildcard searches with luke i am getting desired results.
But when i do t
You get to decide:
class QueryParser extends QueryParserBase:
/**
* Set to true to allow leading wildcard characters.
*
* When set, * or ? are allowed as
* the first character of a PrefixQuery and WildcardQuery.
* Note that this can produce very slow
* queries on big indexes.
*
* Default
I've used Lucene 2,3 and now 4... i used to believe that * wildcard on the
begining was acepted since 3 (but never used) and reviewing documentation says
"Note: You cannot use a * or ? symbol as the first character of a search." is
that ok or is a missupdated no
's reasonable that "block-major" won't find anything.
>> "block-major-57" should match.
>>
>
> Thank you Ian, I understand. But my question is why wouldn't "
> block-major** *" match?, please note the wildcard at the end! Thanks.
>
On Fri, Sep 20, 2013 at 6:11 PM, Ian Lea wrote:
> It's reasonable that "block-major" won't find anything.
> "block-major-57" should match.
>
Thank you Ian, I understand. But my question is why wouldn't "
block-major** *" match?, pleas
It's reasonable that "block-major" won't find anything.
"block-major-57" should match.
The split into block and major-57 will be because, from the javadocs
for ClassicTokenizer, "Splits words at hyphens, unless there's a
number in the token, in which case the whole token is interpreted as a
produc
Sorry, hit the send button accidentally the last time. Please read below :
Hello,
We're using lucene 4.1. We have the word "*block-major-57*"
indexed. Using the classic analyzer, we get the following tokens : *block*and
*major-57*.
I search for *block-major*, *the docume
Hello,
We're using lucene 4.1. We have the word "block-major-5"
indexed. Using the classic analyzer, we get the following tokens : block
and major-5.
However,
--
With Thanks and Regards,
Ramprakash Ramamoorthy,
Chennai, India.
See
http://lucene.apache.org/core/4_3_1/queryparser/org/apache/lucene/queryparser/complexPhrase/ComplexPhraseQueryParser.html
From: Ian Lea
To: java-user@lucene.apache.org
Sent: Tuesday, 27 August 2013, 10:16
Subject: Re: Wildcard in PhraseQuery
See the
See the FAQ:
http://wiki.apache.org/lucene-java/LuceneFAQ#Can_I_combine_wildcard_and_phrase_search.2C_e.g._.22foo_ba.2A.22.3F
--
Ian.
On Tue, Aug 27, 2013 at 5:11 AM, Chuming Chen wrote:
> Hi All,
>
> Can I use wildcard in a phrase query in Lucene/Solr? Can anybody point m
Hi All,
Can I use wildcard in a phrase query in Lucene/Solr? Can anybody point me some
directions to look into?
Thanks,
Chuming
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e
sion.LUCENE_30, "my_field",
> new StandardAnalyzer(Version.LUCENE_30));
> > Query prefixQuery = queryParser.parse("t*");
> > indexSearcher.search(prefixQuery, collector);
> >
> > Why, I don't know. Seems like this would get expanded out into 5
);
>
> Why, I don't know. Seems like this would get expanded out into 5000
> BooleanQueries and since my max clause count is still set to the default 1024
> I should get the exception. But I didn't. So maybe I don't need the filter
> after all?
>
> Next, I need s
refixQuery, collector);
>
> Why, I don't know. Seems like this would get expanded out into 5000
> BooleanQueries and since my max clause count is still set to the default 1024
> I should get the exception. But I didn't. So maybe I don't need the filter
> after all
count is still set to the default 1024 I
should get the exception. But I didn't. So maybe I don't need the filter
after all?
Next, I need scoring to work. I read that with wildcard queries all scores are
set to 1.0 by default. But I read you can use the
QueryParser.setMultiTe
)
However there is a problem with wildcard searching
catno:WRATHCD25*
works, but
catno:WRATHCD-25*
does not
If I amend the analyzer to comment out the initReader() method then
catno:WRATHCD-25*
now works but of course
catno:WRATHCD25
no longer works.
Wham I doing wrong please
public class
ey generally will be treated
>> as spaces.
>>
>> -- Jack Krupansky
>>
>> -Original Message- From: Nicolas Roduit
>> Sent: Friday, February 08, 2013 2:49 AM
>> To: java-user@lucene.apache.org
>> Su
From: Nicolas Roduit
Sent: Friday, February 08, 2013 10:14 AM
To: java-user@lucene.apache.org
Subject: Re: Re: Wildcard in a text field
For instance, I have a list of tags related to a text. Each text with
its list of tags are put in a document and indexed by Lucene. If we
consider that a tag
"text" fields, be
>> sure to use an analyzer that preserves them since they generally will be
>> treated as spaces.
>>
>> -- Jack Krupansky
>>
>> -Original Message- From: Nicolas Roduit
>> Sent: Friday, February 08, 2013 2:4
quot;?" in "string" fields, escape
them with a backslash. But if you want to escape them in "text"
fields, be sure to use an analyzer that preserves them since they
generally will be treated as spaces.
-- Jack Krupansky
-Original Message- From: Nicolas Roduit
in "text" fields, be sure
to use an analyzer that preserves them since they generally will be treated
as spaces.
-- Jack Krupansky
-Original Message-
From: Nicolas Roduit
Sent: Friday, February 08, 2013 2:49 AM
To: java-user@lucene.apache.org
Subject: Wildcard in a text
I'm looking for a way of making a query on words which contain wildcards
(* or ?). In general, we use wildcards in query, not in the text. I
haven't find anything in Lucene to build that.
-
To unsubscribe, e-mail: java-user-uns
On Sat, Jan 5, 2013 at 4:06 AM, Klaus Nesbigall wrote:
> The actual behavior doesn't work either.
> The english word families will not be found in case the user types the query
> familie*
> So why solve the problem by postulate one oppinion as right and another as
> wrong?
> A simple flag which
e analysis would destroy the wildcard characters;
> also stemming of parts of terms will never work.
> ...
The actual behavior doesn't work either.
The english word families will not be found in case the user types the query
familie*
So why solve the problem by postulate one oppinion as
A possible workaround could be to modify search terms with wildcard tokens by
stemming them manually and creating a new search string.
Searches for hersen* would be modified to hers* and return what you expect.
Con is of course that you search for more than you specified.
Lars-Erik
This is a well-known problem: Wildcards cannot be analyzed by the query parser,
because the analysis would destroy the wildcard characters; also stemming of
parts of terms will never work. For Solr there is a workaround (MultiTermAware
component), but it is also very limited and only works when
is found
* Search for "Hersen*" -> nothing is found because the analyzer does not run
Similiar examples can be constructed easily if umlauts are involved.
Conclusion:
The search query which contains a wildcard should also be run through the
analyzer, because there are a lot of quer
sues related to "internals" aren't appropriate on
"user" lists.
-- Jack Krupansky
-Original Message-
From: sri krishna
Sent: Tuesday, November 27, 2012 12:36 PM
To: java-user@lucene.apache.org
Subject: How does lucene handle the wildcard and fuzzy queries ?
How does lu
> I'm trying to create a phrase query with wildcard, from the
> forums it seems that the solution is not trivial.
> I'm trying to create the following queries: "this is a
> phrase*" OR "*This is a phrase" and
> Get hits on every possibility where the
, 2012 4:51 AM
To: java-user@lucene.apache.org
Subject: RE: using phrase query with wildcard
It can be both.
-Original Message-
From: Doron Yaacoby [mailto:dor...@gingersoftware.com]
Sent: יום א 22 יולי 2012 11:48
To: java-user@lucene.apache.org
Subject: RE: using phrase query with wildcard
Is
It can be both.
-Original Message-
From: Doron Yaacoby [mailto:dor...@gingersoftware.com]
Sent: יום א 22 יולי 2012 11:48
To: java-user@lucene.apache.org
Subject: RE: using phrase query with wildcard
Is * a placeholder for a term or a part of a term?
-Original Message-
From
Is * a placeholder for a term or a part of a term?
-Original Message-
From: Levin, Ilya [mailto:ilya.le...@hp.com]
Sent: 22 July 2012 11:29
To: java-user@lucene.apache.org
Subject: using phrase query with wildcard
Hi,
I'm trying to create a phrase query with wildcard, from the f
Hi,
I'm trying to create a phrase query with wildcard, from the forums it seems
that the solution is not trivial.
I'm trying to create the following queries: "this is a phrase*" OR "*This is
a phrase" and
Get hits on every possibility where the * resides.
What i
Typically, they index the text in reverse order
as well as forward order (similar to synonyms)
so if you have a term in your field
"reverse", you index "esrever" and now your
leading-wildcard search for "*verse" becomes
a trailing search for "esrev*".
There
Hi,
I have a large index with a field that contains a important number of
terms. I knew that searching with a term starting with a wildcard was not
a good idea; looking at WildcardTermEnum(IndexReader,Term) and
IndexReader.terms(Term) I understand better why now. I have been asked
however by
On 09/03/2012 12:23, Paul Taylor wrote:
On 09/03/2012 10:42, Paul Taylor wrote:
There is a mismatch between the score for a wildcard match and an
exact match
Just found the problem has been reported
https://issues.apache.org/jira/browse/LUCENE-2557 not quite whether
there is a solution
On 09/03/2012 10:42, Paul Taylor wrote:
There is a mismatch between the score for a wildcard match and an
exact match
Just found the problem has been reported
https://issues.apache.org/jira/browse/LUCENE-2557 not quite whether
there is a solution available yet.
Paul
There is a mismatch between the score for a wildcard match and an exact
match
I search for
|recording:live OR recording:luve*
|
And here is the Explain Output from Search
|DocNo:0:1.4196585:-1cf0-4d1f-aca7-2a6f89e34b36
1.4196585 = (MATCH) max plus0.1 times others of:
0.3763506
To: java-user@lucene.apache.org
Subject: RE: Lucene 2.9.4 Wildcard Search, Boost and Sorting
Hi,
all MultiTermQueries are constant score by default since Lucene 2.9, you can
change that back to scoring mode:
WildcardQuery.setRewriteMethod(MultiTermQuery.SCORING_BOOLEAN_QUERY_REWRITE)
This slows
wildcard.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Lutz Fechner [mailto:lfech...@hubwoo.com]
> Sent: Wednesday, February 01, 2012 11:42 AM
> To: java-user@lucene.apache.org
> Subjec
Hi,
I have an issue with Lucene 2.9.4 and sorting of wildcard queries.
If I set a boost to some documents during indexing like this:
doc.setBoost(1000.00);
and execute a query like this:
PRODUCT_GROUP:2020*
I don't get results with a high boost value returned before the documents wit
A google search of "lucene stemming wildcards" finds some hits
implying these don't work well together.
http://lucene.472066.n3.nabble.com/Conflicts-with-Stemming-and-Wildcard-Prefix-Queries-td540479.html
may be a solution.
--
Ian.
On Tue, Nov 29, 2011 at 10:39 AM, SBS wrote:
r in my custom analyser,
> wildcard searches malfunction.
>
> As an example, I have the words "appendicitis" and "sensitisation"
> in our content. When I enter a query of "a*itis" I would expect
> to have "appendicitis" match but ins
> functionality which I also need).
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/PorterStemFilter-causes-wildcard-searches-to-not-work-tp3525790p3544411.html
> Sent from the Lucene - Java Users mailing list archive at Nabble.com.
--
sage in context:
http://lucene.472066.n3.nabble.com/PorterStemFilter-causes-wildcard-searches-to-not-work-tp3525790p3544411.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
getting matches
somewhere other than the field you think you are getting matches on.
Posting your schema and the results of appending &debugQuery=on
would certainly help.
Best
Erick
On Mon, Nov 21, 2011 at 2:41 PM, SBS wrote:
> It seems that when I use a PorterStemFilter in my cust
It seems that when I use a PorterStemFilter in my custom analyser, wildcard
searches malfunction.
As an example, I have the words "appendicitis" and "sensitisation" in our
content. When I enter a query of "a*itis" I would expect to have
"appendicitis" mat
}
} while (termEnum.next());
// adding last term variations
mq.add(qTail.toArray(new Term[] {}));
// mq is now the query you need
Best regards,
Dmitry.
- Original Message -
From: "Ralf Heyde"
To: java-user@lucene.apache.org
Sent: Thursday, October 13, 2011 5:07:20 PM
Subject
Hello,
i'm trying to search the following phase:
I'm searching all occurrences of:
. "The Right Way"
. "The Right Ways"
Possible solutions could be something like this - combining a phrase &
wildcard search:
. title:&quo
Thx!
> -Ursprüngliche Nachricht-
> Von: Uwe Schindler [mailto:u...@thetaphi.de]
> Gesendet: Donnerstag, 30. Juni 2011 10:32
> An: java-user@lucene.apache.org
> Betreff: RE: negative wildcard query
>
> Pure negative queries do not work, you have to add a MUST c
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Clemens Wyss [mailto:clemens...@mysign.ch]
> Sent: Thursday, June 30, 2011 9:44 AM
> To: java-user@lucene.apache.org
> Subject: AW: negative wild
@mysign.ch]
> Gesendet: Donnerstag, 30. Juni 2011 05:37
> An: java-user@lucene.apache.org
> Betreff: AW: negative wildcard query
>
> Karl, I just saw, that I had a typo in my initial post. It should be:
>
> Say I have a document with a single field "f". How can I se
1 - 100 of 417 matches
Mail list logo
