Is accumulo considering row level visibility for read and write (updates).
Basically in one of our application we want user to insert rows with
different visibility options for updating that row vs reading that row. We
want one role to be restricted to just read that row but another special
role to update as well as read that row.

By having read and update visibility accumulo can expose more rows as there
is no fear of them being updated.

I am relatively new user of accumulo and if this is already discussed in
past, can anyone guide me to that discussion?


NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB