Lisheng:
I'm not too up on the details of Lucene block join, but I don't
think it really applies to access control. You'd have to
have documents grouped by access control (i.e. every
child doc of doc X has the same access control). If you
can do that, you can put an "authorization token" in the
Erick, very sorry that i misspelled your name earlier! later i read more
and found that lucene seemed to implement approach 2/ (search a few times
and combine results), i guess when joining becomes complicated the
performance may suffer? later i will try to study more,
thanks for helps, Lisheng
Eric: thanks very much for your quick response (somehow msg was sent to
spam initially, sorry about that)
yes the rules has to be complicated beyond my control, we also tried to
filter after search, but after data amount grows, it becomes slow ..
Rightnow lucene has feature like document block
I know this seems facetious, but Talk to your
clients about _why_ they want such increasingly
complex access requirements. Often the logic
is pretty flawed for the complexity. Things like
"allow user X to see document Y if they're part of
groups A, B, C but not D or E unless they are
also part
Hi, i have been using solr for many years and it is VERY helpful.
My problem is that our app has an increasingly more complicated access
control to satisfy client's requirement, in solr/lucene it means we need
to add more and more fields into each document and use more and more
complicated
