content in different
> indexes/cores.
>
--
View this message in context:
http://lucene.472066.n3.nabble.com/Many-Cores-with-Solr-tp3161889p3986710.html
Sent from the Solr - User mailing list archive at Nabble.com.
ich can handle the auth and
>> adding a query term.
>>
>>> IMO it would be a better (from Solr's perspective) to handle the security
>>> w/ the application code. Each query could include a "?fq=userID:12345..."
>>> which would l
t;
>> which would limit results to only what that user is allowed to see.
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Many-Cores-with-Solr-tp3161889p3986675.html
> Sent from the Solr - User mailing list archive at Nabble.com.
It's a similar approach as using SQL to filter the rows brought back
for a particular user from a table. It's strong as long as you write
your queries correctly, you store your data properly, and you guard
against injection and privilege escalation. There's an added bonus in
this case in that the u
a better (from Solr's perspective) to handle the security
> w/ the application code. Each query could include a "?fq=userID:12345..."
> which would limit results to only what that user is allowed to see.
--
View this message in context:
http://lucene.472066.n3.na
That's what we do. It has the advantage of letting the general queries
be cached once across all users.
Michael
On Tue, May 29, 2012 at 12:39 PM, Klostermeyer, Michael
wrote:
> IMO it would be a better (from Solr's perspective) to handle the security w/
> the application code. Each query could
ilto:mikeadougl...@gmail.com]
Sent: Wednesday, May 23, 2012 4:02 PM
To: solr-user@lucene.apache.org
Subject: Re: Many Cores with Solr
My interest in this is the desire to create one index per user of a system -
the issue here is privacy - data indexed for one user should not be visible to
other u
like a valid/feasible approach?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Many-Cores-with-Solr-tp3161889p3985789.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hi Torsten,
On Tue, Jul 12, 2011 at 2:45 PM, Torsten Kunze wrote:
> Hi,
>
> as a feasibility study I am trying to run Solr with multiple thousands of
> cores in the same shard to have small indexes that can be created and
> removed very fast.
> Now, I have a Tomcat running with 1.600 cores. Memor
Hi,
as a feasibility study I am trying to run Solr with multiple thousands of cores
in the same shard to have small indexes that can be created and removed very
fast.
Now, I have a Tomcat running with 1.600 cores. Memory and open file handles
have been adjusted to be enough for that scenario.
10 matches
Mail list logo