There is a performance difference. You have an upper bound of returning all data to the client be scanned, even with a FirstEntryInRowIterator. Imagine a table layout where each Key/Value pair represents a single row or document. Using a counting iterator will return a count (most likely a 64-bit long) for each tablet, that the client can then add together.
There is a deleteRows feature (TableOperations#deleteRows) which may be what you want. It avoids having to bring data back to the client. On Thu, Nov 12, 2015 at 9:23 AM, z11373 <[email protected]> wrote: > Thanks all for the reply. > > @Josh: Is my understanding correct that iterating the rows to get the count > on client side and server side doesn't have significant performance diff? > > Besides counting iterator, I'd like to see if we can add feature for > deleting in bulk? Right now, I have to go thru each of them, and then call > putDelete from client. I wish there is a magic way to tell server to delete > all rows for this specific range. > > > Thanks, > Z > > > > -- > View this message in context: > http://apache-accumulo.1065345.n5.nabble.com/total-table-rows-tp15484p15535.html > Sent from the Developers mailing list archive at Nabble.com. >
