Re: Preparing the ground for a real multilang index

[Paul Libbrecht]

Can't the copy field use a different analyzer?
Both for query and indexing?



paul

Le 08-juil.-09 à 02:36, Michael Lackhoff a écrit :

Otherwise you need to craft your own analyzer which reads the language from the field-name... there's several classes ready for this.

On 08.07.2009 00:50 Jan Høydahl wrote:

itself and do not need to know the query language. You may then want

field-to-rule-them-all search.

to do a copyfield from all your text_<lang> -> text for convenient one-

yet analyzed field value. I cannot see yet the advantage of this

all, so it would miss many hits. Or is there a way to combine many

all of them at once? That would be great indeed!

-Michael

Would that really help? As I understand it, copyfield takes the raw, not "text"-field over the current situation with no text_<lang> fields at all. The copied-to text field has to be language agnostic with no stemming at differently stemmed variants into one field to be able to search against

smime.p7s
Description: S/MIME cryptographic signature