A problem with this as recently surfaced: spelling suggestions. A
spelling checker built from the index pulls all terms. You cannot give
it a filter query. But, you don't want to show people words from
documents they should not see.
On Fri, Aug 27, 2010 at 12:01 PM, Lance Norskog wrote:
> User se
User security tends to change often. You may find it easier to use
user/role security. You could create a unique role for a user's docs
and store that role instead. You need a separate user->role database.
Later, the user can choose to share docs with someone else and you
would then change the mapp
my feeling is that private fields in a public document will be the hardest
nut to crack, unless you have an intermediary layer that users call instead
of hitting your solr instance directly. If you front it with a web service
you could handle various authorization scenarios a little easier.
Priva
