Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # user >> HBase type support


Copy link to this message
-
Re: HBase type support
On Fri, Mar 15, 2013 at 10:45 PM, lars hofhansl <[EMAIL PROTECTED]> wrote:

> I think generally we should keep HBase a byte[] based key value store.
> What we should add to HBase are tools that would allow client side apps
> (or libraries) to built functionality on top of plain HBase.
>

That's precisely it. HBase is not changed in any fundamental way to
acknowledge or enforce types. Instead, the hbase-client module makes type
management easier for user code.

Serialization that maintains a correct semantic sort order is important as
> a building block, so is code that can build up correctly serialized and
> sortable compound keys, as well as hashing algorithms.
>

Agreed on serialization. Hashing I can do without. Yes it's a common
practice, but IMHO, if you're hashing, you're not taking advantage of the
natural distribution of your data. I think it's a lazy schema designer's
approach. I see no problem with shipping with support for some hashing
strategies if users demand, but I don't think it's a design approach we
should encourage.

Thanks,
Nick

________________________________
>  From: Nick Dimiduk <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Sent: Friday, March 15, 2013 10:57 AM
> Subject: Re: HBase type support
>
> I'm talking about MD5, SHA1, etc. It's something explicitly mentioned
> in HBASE-7221.
>
> On Fri, Mar 15, 2013 at 10:55 AM, James Taylor <[EMAIL PROTECTED]
> >wrote:
>
> > Hi Nick,
> > What do you mean by "hashing algorithms"?
> > Thanks,
> > James
> >
> >
> > On 03/15/2013 10:11 AM, Nick Dimiduk wrote:
> >
> >> Hi David,
> >>
> >> Native support for a handful of hashing algorithms has also been
> >> discussed.
> >> Do you think these should be supported directly, as opposed to using a
> >> fixed-length String or fixed-length byte[]?
> >>
> >> Thanks,
> >> Nick
> >>
> >> On Thu, Mar 14, 2013 at 9:51 AM, David Koch <[EMAIL PROTECTED]>
> >> wrote:
> >>
> >>  Hi Nick,
> >>>
> >>> As an HBase user I would welcome this addition. In addition to the
> >>> proposed
> >>> list of datatypes A UUID/GUID type would also be nice to have.
> >>>
> >>> Regards,
> >>>
> >>> /David
> >>>
> >>>
> >>> On Wed, Mar 13, 2013 at 5:42 PM, Nick Dimiduk <[EMAIL PROTECTED]>
> >>> wrote:
> >>>
> >>>  Hi all,
> >>>>
> >>>> I'd like to draw your attention to HBASE-8089. The desire is to add
> type
> >>>> support to HBase. There are two primary objectives: make the lives of
> >>>> developers building on HBase easier, and facilitate better tools on
> top
> >>>>
> >>> of
> >>>
> >>>> HBase. Please chime in with any feature suggestions you think we've
> >>>>
> >>> missed
> >>>
> >>>> in initial conversations.
> >>>>
> >>>> Thanks,
> >>>> -n
> >>>>
> >>>> [0]: https://issues.apache.org/**jira/browse/HBASE-8089<
> https://issues.apache.org/jira/browse/HBASE-8089>
> >>>>
> >>>>
> >
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB