I had earlier posted a similar discussion in LinkedIn and David Smiley
rightly advised me that solr-user is a better place for technical
discussions
----------------------------------
Our product which is hosted supports searching on educational resources. Our
customers can choose to make specific resources unavailable for their users
and also it depends on licensing. Our current solution uses full text search
support in the database and handles availability as part of sql .
My task is to move the search from the database full text search into Solr.
I searched through posts and found some that were kind of related and I am
thinking along the following lines
a) Use the authorization model. I can add fields like allow and/or deny
in the index which contain the list of customers. At query time, I can add
the constraint based on the customer Id. I am concerned about the
performance if there are lot of values for these fields and also it requires
constant reindexing if a value in this field changes
b) Use Query-time Join.
Have the resource to availability for customer in separate inner
documents.
We are planning to deploy in SolrCloud. I have read some challenges
about Query-time join and SolrCloud. So this may not work for us.
c) Other ideas?
Excerpts from David Smiley's response
You're right that there may be some re-indexing as security rules change. If
many Lucene/Solr documents share identical access control with other
documents, then it may make more sense to externally determine which unique
set of access-control sets the user has access to, then finally search by id
-- which will hopefully not be a huge number. I've seen this done both
externally and with a Solr core to join on.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Document-Security-Model-Question-tp4101078.html
Sent from the Solr - User mailing list archive at Nabble.com.
