It is an interesting thought to provide an service in which authorized
users can provide jar(s) containing Accumulo iterators to be dynamically
loaded and available on request. Could have a lot of merit coupled
ACCUMULO-708.
Regardless, I like the general idea of a classloader outside of the
cluster's local filesystem. That does open the door to a lot more
difficult problems as John alluded.
I do believe it's worth noting that security is only one application of
cell-level visibility. Using visibilities/authorizations as a filtering
mechanism for application logic is an intriguing subject.
On 8/8/2012 2:57 PM, Benson Margulies wrote:
Is this stuff remotely relevant to the question of how to manage
iterator code in a safe and organized way?
