Re: Automatic analyzer resolving based on Locale

2007-05-09 Thread Chris Hostetter
: - Use an IndexEverythingAnalyzer for writing, : so "werk", "werkte", "gewerkt" and "en" is indexed as-is when they are : encountered. : : - And then use a DutchAnalyzer for reading, : which if I ask "werk" searches for "werk", "werkte" and "gewerkt", : and also ignores stop words like "en" in th

Re: Automatic analyzer resolving based on Locale

2007-05-09 Thread Erick Erickson
Well, I don't see how this can work. In your example, you'd index "werkte". But how are you going to search such that this matches "werk"? No matter what analyzers you use? It looks like you're thinking about either stemming or wildcarding, but I really suspect that stemming is language dependent.

Re: Automatic analyzer resolving based on Locale

2007-05-09 Thread Geoffrey De Smet
We 'd use a different index for each locale's language that is configured, however this might have an impact on performance. Would this be attainable (maybe some day in lucene)? - Use an IndexEverythingAnalyzer for writing, so "werk", "werkte", "gewerkt" and "en" is indexed as-is when they are

Re: Automatic analyzer resolving based on Locale

2007-05-08 Thread Chris Hostetter
: There is nothing canned that I know of. I'm also not sure how this : would be used. If you're using a single index, how are you going : to index, then search using these analyzers? Or is there some : other magic going on? i suspect the use case is "shipped" software product, where you want to h

Re: Automatic analyzer resolving based on Locale

2007-05-08 Thread Erick Erickson
There is nothing canned that I know of. I'm also not sure how this would be used. If you're using a single index, how are you going to index, then search using these analyzers? Or is there some other magic going on? Consider your document with a field "text". If you index into this field with dif