You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by john smith <js...@gmail.com> on 2010/06/22 04:06:05 UTC
Distributed Cache for HBase table
Hey all,
I am not sure whether this is feasible or not .
How about having a "Distributed Cache" for Hbase table, where we can just
specify the table name (or a subset of it's columns) and it gets copied to
all the nodes in the cluster during the mapreduce job. Does anything similar
to this already exists in HBase . This feature can be useful if we want to
do any processing on very small tables. I tried searching for this but
didn't find anything relevant.
Any ideas/comments ?
Thanks
jS
Re: Distributed Cache for HBase table
Posted by Dhruba Borthakur <dh...@gmail.com>.
are you proposing that internally it increases the replication factor of all
the Hfiles for that table?
On Mon, Jun 21, 2010 at 7:06 PM, john smith <js...@gmail.com> wrote:
> Hey all,
>
> I am not sure whether this is feasible or not .
> How about having a "Distributed Cache" for Hbase table, where we can just
> specify the table name (or a subset of it's columns) and it gets copied to
> all the nodes in the cluster during the mapreduce job. Does anything
> similar
> to this already exists in HBase . This feature can be useful if we want to
> do any processing on very small tables. I tried searching for this but
> didn't find anything relevant.
>
> Any ideas/comments ?
>
> Thanks
> jS
>
--
Connect to me at http://www.facebook.com/dhruba
Re: Distributed Cache for HBase table
Posted by Todd Lipcon <to...@cloudera.com>.
You may be interested in the following JIRA:
http://issues.apache.org/jira/browse/hbase-2357
However note that at this point it's just an idea - no one's working on it.
-Todd
On Mon, Jun 21, 2010 at 7:06 PM, john smith <js...@gmail.com> wrote:
> Hey all,
>
> I am not sure whether this is feasible or not .
> How about having a "Distributed Cache" for Hbase table, where we can just
> specify the table name (or a subset of it's columns) and it gets copied to
> all the nodes in the cluster during the mapreduce job. Does anything
> similar
> to this already exists in HBase . This feature can be useful if we want to
> do any processing on very small tables. I tried searching for this but
> didn't find anything relevant.
>
> Any ideas/comments ?
>
> Thanks
> jS
>
--
Todd Lipcon
Software Engineer, Cloudera