If you only have 2 languages this approach might work for you. This
is not something I would consider with the number of languages I need
to support.
Eli
On Thu, May 8, 2008 at 5:51 AM, Gereon Steffens <[EMAIL PROTECTED]> wrote:
>
>
> > These are shards of one index and not multiple indexes. Th
Using distributed search to solve the language problem is very similar
to using multiple fields to solve it. You need different analyzers
for each language, and that gives you another way to have just that;
trading management of multiple fields for management of multiple cores
or shards. In your
These are shards of one index and not multiple indexes. There is
probably a way to get each shard to contain one language but then you
end up with x servers for x languages, and some will be under utilized
while other will be over utilized.
Schemas will be identical, except for analysers. The l
I don't really see how that would help, no. All the benefits from
using separate indices would be gained by using one field per
language, ISTM.
By the way, there are tools available that make field-per-language
stuff much easier, especially if there are many fields. By using
dynamic fie
e] 303.271.9100
[Fax] 303.271.1930
[E-Mail] [EMAIL PROTECTED]
NYSE: TYL
www.tyler-eagle.com
-Original Message-
From: Eli K [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 07, 2008 2:35 PM
To: solr-user@lucene.apache.org
Subject: Re: multi-language searching with Solr
Gereon,
I think that yo
Gereon,
I think that you must have the same schema on each shard but I am not
sure if it must also have the same analyzers.
These are shards of one index and not multiple indexes. There is
probably a way to get each shard to contain one language but then you
end up with x servers for x languages,
I have the same requirement, and from what I understand the distributed
search feature will help implementing this, by having one shard per
language. Am I right?
Gereon
Mike Klaas wrote:
On 5-May-08, at 1:28 PM, Eli K wrote:
Wouldn't this impact both indexing and search performance and the
On 5-May-08, at 1:28 PM, Eli K wrote:
Wouldn't this impact both indexing and search performance and the size
of the index?
It is also probable that I will have more then one free text fields
later on and with at least 20 languages this approach does not seem
very manageable. Are there other opt
PROTECTED]
Verzonden: dinsdag 6 mei 2008 18:26
Aan: solr-user@lucene.apache.org
Onderwerp: Re: multi-language searching with Solr
Peter,
Thanks for your help, I will prototype your solution and see if it
makes sense for me.
Eli
On Mon, May 5, 2008 at 5:38 PM, Binkley, Peter
<[EMAIL PROTEC
-
> From: Eli K [mailto:[EMAIL PROTECTED]
>
> Sent: Monday, May 05, 2008 2:28 PM
> To: solr-user@lucene.apache.org
>
>
> Subject: Re: multi-language searching with Solr
>
> Wouldn't this impact both indexing and search performance and the size
> of the
I searched the Solr list but not as much the Lucene list. I will look
again to see if there is something there that might work with Solr. I
rather leverage Solr, but if I have no choice I will to do this using
Lucene only.
Thanks,
Eli
On Mon, May 5, 2008 at 4:58 PM, Erick Erickson <[EMAIL PROT
al Message-
From: Eli K [mailto:[EMAIL PROTECTED]
Sent: Monday, May 05, 2008 2:28 PM
To: solr-user@lucene.apache.org
Subject: Re: multi-language searching with Solr
Wouldn't this impact both indexing and search performance and the size
of the index?
It is also probable that I will have
You might want to bounce over to the Lucene user's list and search
for language. This topic has arisen many times and there's some good
discussion. And have you searched the solr users list of "language"? I
know it's turned up here as well.
Best
Erick
On Mon, May 5, 2008 at 4:28 PM, Eli K <[EMAIL
Wouldn't this impact both indexing and search performance and the size
of the index?
It is also probable that I will have more then one free text fields
later on and with at least 20 languages this approach does not seem
very manageable. Are there other options for making this work with
stemming?
I think you would have to declare a separate field for each language
(freetext_en, freetext_fr, etc.), each with its own appropriate
stemming. Your ingestion process would have to assign the free text
content for each document to the appropriate field; so, for each
document, only one of the freetex
15 matches
Mail list logo
