about which
approach might be better for the given use case.
>
> Regards.
>
> Shushuai
>
>
> ____
> From: Lajos
> To: solr-user@lucene.apache.org
> Sent: Saturday, March 15, 2014 1:19 PM
> Subject: Re: Best prac
to:ss...@yahoo.com]
Sent: Saturday, March 15, 2014 11:18 AM
To: solr-user@lucene.apache.org
Subject: Re: Best practice to support multi-tenant with Solr
Hi Lajos, thanks again.
Your suggestion is to support multi-tenant via collection in a Solr Cloud:
putting small tenants in one collection and
Shushuai
From: Lajos
To: solr-user@lucene.apache.org
Sent: Saturday, March 15, 2014 1:19 PM
Subject: Re: Best practice to support multi-tenant with Solr
Hi Shushuai,
---
Finally, I would (in general) argue for cloud-based implementations to give you
data
os
>
>
> From: Lajos
> To: solr-user@lucene.apache.org
> Sent: Saturday, March 15, 2014 5:37 AM
> Subject: Re: Best practice to support multi-tenant with Solr
>
>
> Hi Shushuai,
>
> Just a few thoughts.
>
> I would guess t
rday, March 15, 2014 5:37 AM
Subject: Re: Best practice to support multi-tenant with Solr
Hi Shushuai,
Just a few thoughts.
I would guess that most people would argue for implementing
multi-tenancy within your core (via some unique filter ID) or collection
(via document routing) because of
-sharding to have multiple replicas of cores
(corresponding to tenants) across nodes?
Shushuai
From: Lajos
To: solr-user@lucene.apache.org
Sent: Saturday, March 15, 2014 5:37 AM
Subject: Re: Best practice to support multi-tenant with Solr
Hi Shushuai,
Just
Hi Shushuai,
Just a few thoughts.
I would guess that most people would argue for implementing
multi-tenancy within your core (via some unique filter ID) or collection
(via document routing) because of the headache of managing individual
cores at the scale you are talking about.
There are di
