For scenario 1-3, it is a very small dataset that we will be adding/hiding. In addition, we would rather not duplicate Accumulo's Authorization code into our project to filter what should or should not be hidden from the user given our scenarios.
Going through this entire thread, am I wrong to assume that Accumulo will not be accepting this patch? If so, please let us know so we can come up with alternative ways to solve our use cases. -- View this message in context: http://apache-accumulo.1065345.n5.nabble.com/NOT-operator-in-visibility-string-tp7949p8317.html Sent from the Users mailing list archive at Nabble.com.
