You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by yeshwanth kumar <ye...@gmail.com> on 2014/09/17 22:38:59 UTC
is it a gud way to store a map object in hbase column
hi i have a huge map object, which comes from the solr query results.
map contains around 400-500 key-value pairs
is it a gud way to store the entire map as a value in the column.
is there any particular things like column vaue size, i need to take care of
or shud i store it in different columns with dynamic column names
storing the map object makes task easy.
but want know,which way is preferable.
thanks,
Yeshwanth
Re: is it a gud way to store a map object in hbase column
Posted by Nick Dimiduk <nd...@gmail.com>.
You may be able to achieve the desired effect by implementing a custom
Filter#transformCell(Cell).
-n
On Thu, Sep 18, 2014 at 1:19 PM, Ted Yu <yu...@gmail.com> wrote:
> bq. query in the map-object like the way we query for column values
>
> Other than storing map-object using multiple columns, I am not aware of
> such queries.
>
> Cheers
>
> On Thu, Sep 18, 2014 at 10:10 AM, yeshwanth kumar <ye...@gmail.com>
> wrote:
>
> > hi ted,
> >
> > i may not need all the key-value pairs,
> > is there any way can we query in the map-object like the way we query for
> > column values in hbase.
> >
> > -yeshwanth
> >
> > Cheers,
> > Yeshwanth
> >
> >
> > On Thu, Sep 18, 2014 at 3:14 AM, Ted Yu <yu...@gmail.com> wrote:
> >
> > > bq. storing the map object makes task easy.
> > >
> > > The above makes write(s) easy. But when you query, do you always need
> all
> > > the key-value pairs in this map object ?
> > >
> > > Cheers
> > >
> > > On Wed, Sep 17, 2014 at 1:38 PM, yeshwanth kumar <
> yeshwanth43@gmail.com>
> > > wrote:
> > >
> > > > hi i have a huge map object, which comes from the solr query results.
> > > > map contains around 400-500 key-value pairs
> > > >
> > > > is it a gud way to store the entire map as a value in the column.
> > > > is there any particular things like column vaue size, i need to take
> > care
> > > > of
> > > > or shud i store it in different columns with dynamic column names
> > > >
> > > > storing the map object makes task easy.
> > > > but want know,which way is preferable.
> > > >
> > > > thanks,
> > > > Yeshwanth
> > > >
> > >
> >
>
Re: is it a gud way to store a map object in hbase column
Posted by Ted Yu <yu...@gmail.com>.
bq. query in the map-object like the way we query for column values
Other than storing map-object using multiple columns, I am not aware of
such queries.
Cheers
On Thu, Sep 18, 2014 at 10:10 AM, yeshwanth kumar <ye...@gmail.com>
wrote:
> hi ted,
>
> i may not need all the key-value pairs,
> is there any way can we query in the map-object like the way we query for
> column values in hbase.
>
> -yeshwanth
>
> Cheers,
> Yeshwanth
>
>
> On Thu, Sep 18, 2014 at 3:14 AM, Ted Yu <yu...@gmail.com> wrote:
>
> > bq. storing the map object makes task easy.
> >
> > The above makes write(s) easy. But when you query, do you always need all
> > the key-value pairs in this map object ?
> >
> > Cheers
> >
> > On Wed, Sep 17, 2014 at 1:38 PM, yeshwanth kumar <ye...@gmail.com>
> > wrote:
> >
> > > hi i have a huge map object, which comes from the solr query results.
> > > map contains around 400-500 key-value pairs
> > >
> > > is it a gud way to store the entire map as a value in the column.
> > > is there any particular things like column vaue size, i need to take
> care
> > > of
> > > or shud i store it in different columns with dynamic column names
> > >
> > > storing the map object makes task easy.
> > > but want know,which way is preferable.
> > >
> > > thanks,
> > > Yeshwanth
> > >
> >
>
Re: is it a gud way to store a map object in hbase column
Posted by yeshwanth kumar <ye...@gmail.com>.
hi ted,
i may not need all the key-value pairs,
is there any way can we query in the map-object like the way we query for
column values in hbase.
-yeshwanth
Cheers,
Yeshwanth
On Thu, Sep 18, 2014 at 3:14 AM, Ted Yu <yu...@gmail.com> wrote:
> bq. storing the map object makes task easy.
>
> The above makes write(s) easy. But when you query, do you always need all
> the key-value pairs in this map object ?
>
> Cheers
>
> On Wed, Sep 17, 2014 at 1:38 PM, yeshwanth kumar <ye...@gmail.com>
> wrote:
>
> > hi i have a huge map object, which comes from the solr query results.
> > map contains around 400-500 key-value pairs
> >
> > is it a gud way to store the entire map as a value in the column.
> > is there any particular things like column vaue size, i need to take care
> > of
> > or shud i store it in different columns with dynamic column names
> >
> > storing the map object makes task easy.
> > but want know,which way is preferable.
> >
> > thanks,
> > Yeshwanth
> >
>
Re: is it a gud way to store a map object in hbase column
Posted by Ted Yu <yu...@gmail.com>.
bq. storing the map object makes task easy.
The above makes write(s) easy. But when you query, do you always need all
the key-value pairs in this map object ?
Cheers
On Wed, Sep 17, 2014 at 1:38 PM, yeshwanth kumar <ye...@gmail.com>
wrote:
> hi i have a huge map object, which comes from the solr query results.
> map contains around 400-500 key-value pairs
>
> is it a gud way to store the entire map as a value in the column.
> is there any particular things like column vaue size, i need to take care
> of
> or shud i store it in different columns with dynamic column names
>
> storing the map object makes task easy.
> but want know,which way is preferable.
>
> thanks,
> Yeshwanth
>