Hi Jayesh,
deleteRows(...) is a tablet-level operation, instead of issuing updates (deletes, in this
case) to specific "cells" of the table. Entire portions of the tablets are
dropped. deleteRows() can be very efficient to delete a large contiguous portion of your
table. If you need to selectively delete a certain cell (key-value pair) based on the
visibility, just use the putDelete() method with a Mutation and the BatchWriter. The
BatchDeleter is also an option if you haven't seen it yet.
Does that make sense?
Jayesh Patel wrote:
Why is there no visibility parameter in TableOperations, especially
something like deleteRows()?
All the reads and writes obviously require visibility, and
Mutation.putDelete() does also, so it feels like we’re able to cheat
and deleteRows() that I might not have visibility into.
Thank you,
Jayesh
