Hi Terence,
Terence Gannon schrieb:
Yes, the ownerUid will likely be assigned once and never changed. But
you still need it, in order to keep track of who has contributed which
document.
Yes, of course!
I've been going over some of the simpler query scenarios, and Solr is
capable of handlin
This may be another reason to eventually go
to an external RDBMS.
Thanks very much for your help!
Terence
-Original Message-
From: Michael Ludwig
Sent: May 13, 2009 05:27
To: solr-user@lucene.apache.org
Subject: Re: Selective Searches Based on User Identity
Terence Gannon schrieb:
> Paul -- t
Terence Gannon schrieb:
Paul -- thanks for the reply, I appreciate it. That's a very
practical approach, and is worth taking a closer look at. Actually,
taking your idea one step further, perhaps three fields; 1) ownerUid
(uid of the document's owner) 2) grantedUid (uid of users who have
been g
al Message-
From: Matt Weber [mailto:m...@mattweber.org]
Sent: May 12, 2009 14:41
To: solr-user@lucene.apache.org
Subject: Re: Selective Searches Based on User Identity
Here is a good presentation on search security from the Infonortics
Search Conference that was held a few weeks ag
Here is a good presentation on search security from the Infonortics
Search Conference that was held a few weeks ago.
http://www.infonortics.com/searchengines/sh09/slides/kehoe.pdf
The approach you are using is called early-binding. As Jay mentioned,
one of the downsides is updating the docu
regards...
Terence
-Original Message-
From: Matt Weber [mailto:m...@mattweber.org]
Sent: May 12, 2009 14:06
To: solr-user@lucene.apache.org
Subject: Re: Selective Searches Based on User Identity
I also work with the FAST Enterprise Search engine and this is exactly
how their Security Access
The only downside would be that you would have to update a document anytime
a user was granted or denied access. You would have to query before the
update to get the current values for grantedUID and deniedUID, remove/add
values, and update the index. If you don't have a lot of changes in the
syste
I also work with the FAST Enterprise Search engine and this is exactly
how their Security Access Module works. They actually use a modified
base-32 encoded value for indexing, but that is because they don't
have the luxury of untokenized/un-processed String fields like Solr.
Thanks,
Matt
Paul -- thanks for the reply, I appreciate it. That's a very practical
approach, and is worth taking a closer look at. Actually, taking your idea
one step further, perhaps three fields; 1) ownerUid (uid of the document's
owner) 2) grantedUid (uid of users who have been granted access), and 3)
den
Why can't you simply index a field "authorized-to" with value user-B
and enrich any query you receive from a user with a mandatory query
for that authorization?
paul
Le 11-mai-09 à 17:50, Terence Gannon a écrit :
Can anybody point me in the direction of resources and/or projects
regardi
Can anybody point me in the direction of resources and/or projects regarding
the following scenario; I have a community of users contributing content to
a Solr index. By default, the user (A) who contributes a document owns it,
and can see the document in their search results. The owner can then
11 matches
Mail list logo
