Home | About | Sematext search-lucene.com search-hadoop.com
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
 Search Hadoop and all its subprojects:

Switch to Threaded View
Accumulo >> mail # user >> m.putDelete versus RowDeletingIterator?


Copy link to this message
-
Re: m.putDelete versus RowDeletingIterator?
They do different things.

Deleting mutations marks each entry with a delete marker.  Using the
iterator marks a whole row with a single mutation.

If you have a million entries in your row, the iterator is faster for
the delete, but requires a seek to the start of the row for every
read, so reads are slower.

If your row has one entry, they are the same thing.

Somewhere under N keys... the mutation path will be quite fast, and
still preserve your reading speed.  I'll just pull a number out of
thin air... let's say a few thousand.

-Eric

On Wed, Oct 9, 2013 at 4:01 PM, David Medinets <[EMAIL PROTECTED]> wrote:
> Are there any reason to favor one approach over the other?
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