Deletemany does a scan and selective putDeletes based on the matches to the scan.
Deleterows doesn't use authorizations, because it just drops whole ranges without discrimination of their contents. We don't partition ranges of keys based on authorizations, so deleterows wouldn't be able to make use of this parameter. Your application could do that, if efficient deletes for particular authorizations were essential, by making making an authorization string a prefix of your row, or by partitioning your data into separate tables based on authorizations. But this probably wouldn't be that useful unless all your deletes of this nature were associated with a single authorization which you knew in advance. On Wed, Nov 18, 2015 at 6:10 PM z11373 <z11...@outlook.com> wrote: > Never mind, no longer able to reproduce the issue. > > Why deleterows doesn't support the caller passing authz (unlike deletemany > that has -s)? > Without able to pass the authorization string, I pretty much cannot use > this > command :-( > > Thanks, > Z > > > > -- > View this message in context: > http://apache-accumulo.1065345.n5.nabble.com/delete-rows-test-result-tp15569p15593.html > Sent from the Developers mailing list archive at Nabble.com. >
