Ahhh... I hand't considered that, but you're right - I could probably
parse the blockname...
public class HFile {
public Writer(FileSystem fs, Path path, int blocksize,
Compression.Algorithm compress,
final KeyComparator comparator, BlockCache blockCache)
throws IOException {
this(fs.create(path), blocksize, compress, comparator);
this.closeOutputStream = true;
this.name = path.toString();
this.path = path;
this.blockCache = blockCache;
}
... If I am reading this correctly it looks like the path is used for the
name, that that should have table/cf/ in the beginning. I'll play with
this.
On 7/28/11 5:28 PM, "Stack" <[email protected]> wrote:
>On Thu, Jul 28, 2011 at 2:05 PM, Doug Meil
><[email protected]> wrote:
>> If you iterate through the map in LruBlockCache the keys represent
>>blocknames, but what is the easiest way to go back up the chain (I.e.,
>>StoreFile, CF, Table)?
>>
>>
>
>There is no way to go from the cache to its container? Isn't that a
>good thing? Do block keys have what you need: i.e. do they have table
>name and or cf?
>
>St.Ack
