You'll have a hard time supporting stemming etc with this approach. Perhaps a hybrid solution, querying across the all-languages field and a few selected Language specific fields which receive proper linguistic treatment? qf=text_all text_en^2.0 text_de^1.5
Jan Høydahl On 27. mai 2010, at 06.01, Lance Norskog <goks...@gmail.com> wrote: > If you want to OR a search across many language inputs, you can copy > all of the text into an all-languages field. A pan-language search > would just hit that field. > > On Mon, May 24, 2010 at 9:28 AM, dan sutton <danbsut...@gmail.com> wrote: >> Hi, >> >> I have a requirement to dynamically choose a fieldType to analyze text in >> multiple languages. I will know the language (in a separate field) at index >> and query time. >> >> I've tried implementing this with a custom UpdateRequestProcessorFactory and >> custom DocumentBuilder.toDocument to change the FieldType, but this dosen't >> work. >> >> I realize I can have e.g. text_en, text_de,... and dynamically populate this >> with a custom UpdateRequestProcessorFactory, but we are worried with all the >> languages (lets say 50+) that effectively doing an OR with 50 fields will be >> a performance issue, is this true? >> >> Many thanks in advance, >> Dan >> > > > > -- > Lance Norskog > goks...@gmail.com
