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
Hi,
Probably you have stemmer and it is eating up Capital to capit. Thats the
reason.
Either remove stemmer from analyser chain or add keyword repeat filter.
Ahmet
On Wednesday, October 1, 2014 2:16 PM, Wayne W
wrote:
Hi,
I don't understand this at all. We are indexing some contact names.
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 wildcard sea
12 matches
Mail list logo
