On Fri, Oct 2, 2009 at 6:44 PM, Fergus McMenemie wrote:
> >The copy is done before analysis. The original text is sent to the
> copyField
> >which can choose to do analysis differently from the source field.
> >
> I have been wondering about this as well. The WIKI is not explicit about
> what hap
>On Thu, Oct 1, 2009 at 7:59 PM, Claudio Martella > wrote:
>
>>
>> About the copyField issue in general: as it copies the content to the
>> other field, what is the sense to define analyzers for the destination
>> field? The source is already analyzed so i guess that the RESULT of the
>> analysis i
On Thu, Oct 1, 2009 at 7:59 PM, Claudio Martella wrote:
>
> About the copyField issue in general: as it copies the content to the
> other field, what is the sense to define analyzers for the destination
> field? The source is already analyzed so i guess that the RESULT of the
> analysis is copied
Ok, one more question on this issue. I used to have an "all" field where
i used to copyField "title" "content" and "keywords" defined with
typeField "text", which used to have english-language dependant
analyzers/filters. Now I can copyField all the three "content-*" fields
as I know that only one
Thanks, that's exactly the kind of answer I was looking for.
Chantal Ackermann wrote:
> Hi Claudio,
>
> in schema.xml, the element accepts the attribute type.
> If you need different analyzer chains during indexing and querying,
> configure it like this:
>
>
>
>
>
>
>
>
Hi Claudio,
in schema.xml, the element accepts the attribute type.
If you need different analyzer chains during indexing and querying,
configure it like this:
If there is no difference, just remove one analyzer element and the type
att
Hello list.
So, i setup my schema.xml with the different chains of analyzers and
filters for each field (i.e. i created types text-en, text-de, text-it).
As i have to index documents in different languages, this is good.
But what defines the analyzers and filters for the query?
Let's suppose i
