_type2 that contains a text like "go
to
*mag 78*, class *d* and subclass *99*)
...
dismax
...
100%
field_with_type1
field_with_type_2
...
is not possible? If so, is possible to do that in some other way?
my (query-time) chain. The same
>>>>> doesn't happen at index time...this is my problem...because at index
>>>>> time
>>>>> the field is analyzed exactly as I want...but unfortunately cannot say
>>>>> the
>>>>>
that contains a text like "go
to
*mag 78*, class *d* and subclass *99*)
...
dismax
...
100%
field_with_type1
field_with_type_2
...
is not possible? If so, is possible to do that in some other way?
Sorry for the lon
nerateWordParts="0" generateNumberParts="0"
>>>>> catenateWords="0" catenateNumbers="0" catenateAll="1"
>>>>> splitOnCaseChange="0" />
>>>>>
>>>>>
>&
, is possible to do that in some other way?
Sorry for the long email and thanks again
Andrea
On 08/12/2013 04:01 PM, Jack Krupansky wrote:
Quoted phrases will be passed to the analyzer as one string, so there a
white space tokenizer is needed.
-- Jack Krupansky
-Original Message- Fro
ing, so there a
white space tokenizer is needed.
-- Jack Krupansky
-Original Message- From: Andrea Gazzarini
Sent: Monday, August 12, 2013 6:52 AM
To: solr-user@lucene.apache.org
Subject: Re: Tokenization at query time
Hi Tanguy,
thanks for fast response. What you are saying corresp
pe1) and
>>> second (with type 2) by matching
>>>
>>> - a document which has field_with_type1 equals to *mag78d99* or
>>> - a document which has field_with_type2 that contains a text like "go to
>>> *mag 78*, class *d* and subclass *99*)
>>&g
-- Jack Krupansky
-Original Message- From: Andrea Gazzarini
Sent: Monday, August 12, 2013 6:52 AM
To: solr-user@lucene.apache.org
Subject: Re: Tokenization at query time
Hi Tanguy,
thanks for fast response. What you are saying corresponds perfectly with
the behaviour I'm observing
_with_type1
> field_with_type_2
>
> ...
>
>
> is not possible? If so, is possible to do that in some other way?
>
> Sorry for the long email and thanks again
> Andrea
>
>
> On 08/12/2013 04:01 PM, Jack Krupansky wrote:
>
>> Quoted phrases
Krupansky wrote:
Quoted phrases will be passed to the analyzer as one string, so there
a white space tokenizer is needed.
-- Jack Krupansky
-Original Message- From: Andrea Gazzarini
Sent: Monday, August 12, 2013 6:52 AM
To: solr-user@lucene.apache.org
Subject: Re: Tokenization at
Quoted phrases will be passed to the analyzer as one string, so there a
white space tokenizer is needed.
-- Jack Krupansky
-Original Message-
From: Andrea Gazzarini
Sent: Monday, August 12, 2013 6:52 AM
To: solr-user@lucene.apache.org
Subject: Re: Tokenization at query time
Hi
Hi Tanguy,
thanks for fast response. What you are saying corresponds perfectly with
the behaviour I'm observing.
Now, other than having a big problem (I have several other fields both
in the pf and qf where spaces doesn't matter, field types like the
"text_en" field type in the example schema)
Hello Andrea,
I think you face a rather common issue involving keyword tokenization and query
parsing in Lucene:
The query parser splits the input query on white spaces, and then each token is
analysed according to your configuration.
So those queries with a whitespace won't behave as expected be
13 matches
Mail list logo
