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 >> Record index within a Table


Copy link to this message
-
Re: Record index within a Table
I was thinking a little more on the subject, and convinced myself that I
was wrong.

Since many files on disk correspond to a tablet, the best you can get is
the index of a key-value pair in a given file for a tablet. To get a
sorted stream of key-value pairs for this tablet (to compute index
offset for a key in a tablet), a merged read is performed over all of
those files. Local key offset for a file is meaningless as it does not
imply the correct offset for a tablet.

On 12/3/12 9:30 PM, Josh Elser wrote:
>
> Accumulo doesn't expose any internal offsets of Key-Value pairs
> through the API. While it might be able to extrapolate some of this
> knowledge from the underlying structure of Accumulo, that isn't the
> intent of what Accumulo is trying to provide.
>
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