That was one of my concerns. To date I've been using lucene directly and
pointing it at an index for the current authenticated user. solr cores
seemed to come close to that.
Is the issue with a lot of cores just creating a lot or using many cores
concurrently?
Erik Hatcher-4 wrote
>
> You do g
In our particular case, we're using this index to do prefix searches
for autocomplete of sparse keyword data, so we don't have much to
worry about on this front, but I do agree that it's a consideration
for those use cases that do reveal information via ranking.
Michael Della Bitta
--
You do get relevancy related "leakage" though. With users content all in the
same index and using the same field names, term and document frequencies across
the index will be used for scoring. This may be (and has been) a good reason
to keep separately searchable content in different indexes/c
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
Thank you.
That sounds good - are we sure to get no leakage with this approach?
I'd be indexing personal information which must not be delivered without
authentication.
The solr instance is front-ended by bedework which can handle the auth and
adding a query term.
> IMO it would be a better (fr
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
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 users.
For this purpose solr will be hidden behind a proxy which steers
authenticated sessions to the appropriat ecore.
Does this seem
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
