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 15FDCD479 for ; Fri, 15 Mar 2013 17:12:46 +0000 (UTC) Received: (qmail 64985 invoked by uid 500); 15 Mar 2013 17:12:44 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 64876 invoked by uid 500); 15 Mar 2013 17:12:43 -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 64867 invoked by uid 99); 15 Mar 2013 17:12:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Mar 2013 17:12:43 +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 (nike.apache.org: domain of ndimiduk@gmail.com designates 209.85.128.172 as permitted sender) Received: from [209.85.128.172] (HELO mail-ve0-f172.google.com) (209.85.128.172) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Mar 2013 17:12:38 +0000 Received: by mail-ve0-f172.google.com with SMTP id cz11so2799761veb.31 for ; Fri, 15 Mar 2013 10:12:17 -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=A+cOVCAh+9hTfUNzaAS3gnrW5mTWPUKY62Vy5pwO1gg=; b=FoJTn1W2yd3NWamKpVgK8bAwhiE6wbBQmkGasSuROpFVRpqXnz700QTBCSAwxJlLiJ x9cQ6ErUjOoIeH8NJxbw23PF58vFh/fei9w5Ev22nrtQ7vLelEPcXGZdxOQYRMKsMAdt pr7lNt/zUDj/MjHgTwVg87i2krAIcdh/HuZIBs+AU8F8xMXjlrSI1tdaElhJtApxvjvW 1T+9SLfFmUeniKrXRqGx/7+shEZIcQw1foJ6HhKFRPPr8nqa3ZPBoNO8FWU0D7x9BbzO 6FFfhMlUhNBgpNTktjhAbQLFIhvYLatscHbsYusp79N+Eu+lenvLh6CSXCztjeXAWfaR 63rw== X-Received: by 10.220.223.202 with SMTP id il10mr8027808vcb.4.1363367537389; Fri, 15 Mar 2013 10:12:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.255.129 with HTTP; Fri, 15 Mar 2013 10:11:57 -0700 (PDT) In-Reply-To: References: From: Nick Dimiduk Date: Fri, 15 Mar 2013 10:11:57 -0700 Message-ID: Subject: Re: HBase type support To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=14dae9cdc487c3b93104d7f9bd02 X-Virus-Checked: Checked by ClamAV on apache.org --14dae9cdc487c3b93104d7f9bd02 Content-Type: text/plain; charset=UTF-8 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 > > > --14dae9cdc487c3b93104d7f9bd02--