Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@accumulo.apache.org
Received-SPF: pass (athena.apache.org: domain of josh.elser@gmail.com
 designates 209.85.216.41 as permitted sender)
Message-ID: <50BE36D3.9020602@gmail.com>
Date: Tue, 04 Dec 2012 12:45:55 -0500
From: Josh Elser <josh.elser@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
 rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: user@accumulo.apache.org
Subject: Re: Record index within a Table
References: <50BD5A38.5080505@playstation.sony.com>
 <50BD6042.4050708@gmail.com>
In-Reply-To: <50BD6042.4050708@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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.
>