hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Groschupf ...@media-style.com>
Subject Re: HBase Design Ideas, terminology
Date Mon, 05 Jun 2006 12:24:25 GMT

> Storing namenode and MapReduce status in a BigTable-like structure is
> intriguing,
> but seems dangerous.  (All the database stuff is built on top of DFS
> and MapReduce.  What happens when the database needs a file in DFS,
> which needs a record from the database?  Oh lord...)

Right, I missed that. :-) In general I also completely agree also  
with Andrzej, having HBase as a independent component using io, rpc,  
dfs and map reduce is the way we should go.


View raw message