Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4FCB3E772 for ; Fri, 15 Mar 2013 17:58:33 +0000 (UTC) Received: (qmail 23650 invoked by uid 500); 15 Mar 2013 17:58:31 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 23591 invoked by uid 500); 15 Mar 2013 17:58:31 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 23583 invoked by uid 99); 15 Mar 2013 17:58:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Mar 2013 17:58:31 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ndimiduk@gmail.com designates 209.85.128.181 as permitted sender) Received: from [209.85.128.181] (HELO mail-ve0-f181.google.com) (209.85.128.181) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Mar 2013 17:58:27 +0000 Received: by mail-ve0-f181.google.com with SMTP id d10so2814355vea.40 for ; Fri, 15 Mar 2013 10:58:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=AAIYxAfZgGYJ2f1ZKeQ2vTvtc8p3cwq/mA/tsStEz7A=; b=d9hlYRGfJoskJfKXCgQYIggeo297zMXOHG8ilf08CWY2me4uR40mU0Tleqa96NWHd0 rr9BjlqRnQoYFRG7MnY6zfL4NDdVo4cFeQOl52pIhTWxMCY0q98fwjWpyw/le/h/nLBh cV+tBumoP9bacnE1TR9NONX5KL5eWJmX8rh3Ab12lPJRm9RdAB31LMviB41WiLV+Df77 YNfab/bfOAIswHjK/f7zrlebP7Q/cwXqOPbejeGsuTs8RJeC+6hbOX1nw4N/GG7uEnqO TS3f7T4lANDR1cAN39pnwf0kogqDp8kZ6PsHSqreqDrGi23kb+aulQubQCdL9ejs0GNU ERow== X-Received: by 10.52.100.163 with SMTP id ez3mr7090798vdb.6.1363370286511; Fri, 15 Mar 2013 10:58:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.255.129 with HTTP; Fri, 15 Mar 2013 10:57:46 -0700 (PDT) In-Reply-To: <51436095.6030506@salesforce.com> References: <51436095.6030506@salesforce.com> From: Nick Dimiduk Date: Fri, 15 Mar 2013 10:57:46 -0700 Message-ID: Subject: Re: HBase type support To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=20cf307ca044a000b004d7fa61ba X-Virus-Checked: Checked by ClamAV on apache.org --20cf307ca044a000b004d7fa61ba Content-Type: text/plain; charset=UTF-8 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 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 >> 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 >>> 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 >>>> >>>> > --20cf307ca044a000b004d7fa61ba--