> Alternatively, if one of the "regular" analyzers works for you *except*
> for lower-casing, just use that one for your mixed-case field and
> lower-case your input and send it to your lower-case field.
>
> Be careful to do the same steps when querying .
>
Thanks Erick, I didn't think about this.
See PerFieldAnalyzerWrapper for an easy way to implement two fields
in the same document processed with different analyzers. So basically
you're copying the input to two fields that handle things slightly
differently.
As far as re-implementing stuff, no real re-implementing is necessary,
> I just want to see if it's safe to use two different analyzers for the
> following situation:
>
> I have an index that I want to preserve case with so I can do
> case-sensitive
> searches with my WhitespaceAnalyzer. However, I also want to do case
> insensitive searc
Lynch wrote:
> I just want to see if it's safe to use two different analyzers for the
> following situation:
>
> I have an index that I want to preserve case with so I can do
> case-sensitive
> searches with my WhitespaceAnalyzer. However, I also want to do case
> insen
I just want to see if it's safe to use two different analyzers for the
following situation:
I have an index that I want to preserve case with so I can do case-sensitive
searches with my WhitespaceAnalyzer. However, I also want to do case
insensitive searches.
What I did was create a c
Hi Itamar,
On 01/31/2008 at 6:28 PM, Itamar Syn-Hershko wrote:
> Since Analyzer is set per IndexWriter, which is being added a Document,
> which has several fields, I was wondering how would I store 2 different
> fields in a Document, each being passed through a different Analyzer?
> The idea is t
Hi all,
Since Analyzer is set per IndexWriter, which is being added a Document,
which has several fields, I was wondering how would I store 2 different
fields in a Document, each being passed through a different Analyzer? The
idea is to have 2 fields of the same content, one stemmed and one is not
L PROTECTED]
>>
>>
>
>
> --
> Paulo E. A. Silveira
> Caelum Ensino e Soluções em Java
> http://www.caelum.com.br/
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
CTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Writing-a-document-using-two-different-Analyzers-tf3814647.html#a11194791
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 5/25/07, karl wettin <[EMAIL PROTECTED]> wrote:
PerFieldAnalyzerWrapper
that was fast! thanks!
http://lucene.zones.apache.org:8080/hudson/job/Lucene-Nightly/javadoc/
org/apache/lucene/analysis/PerFieldAnalyzerWrapper.html
--
karl
---
25 maj 2007 kl. 09.32 skrev Paulo Silveira:
I have a Document with tow fields: one I would like to write with
SimpleAnalyzer, the other I want to use StandardAnalyzer, is there a
simple way to do it?
PerFieldAnalyzerWrapper
http://lucene.zones.apache.org:8080/hudson/job/Lucene-Nightly/javad
Hello!
I have a Document with tow fields: one I would like to write with
SimpleAnalyzer, the other I want to use StandardAnalyzer, is there a
simple way to do it?
thanks
--
Paulo E. A. Silveira
Caelum Ensino e Soluções em Java
http://www.caelum.com.br/
-
another
: analyzer for searcher. If I do like this will I get my required result or
: not.. Most importantly I would like to know is this a good practice to have
: two different analyzers for two operations or same analyzer..
There are certainly legitimate cases where it makes sense to have
differnet
another
analyzer for searcher. If I do like this will I get my required result or
not.. Most importantly I would like to know is this a good practice to have
two different analyzers for two operations or same analyzer..
Thanks
Ravi Kumar Jaladanki
14 matches
Mail list logo
