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 2E576963C for ; Mon, 27 Feb 2012 16:14:33 +0000 (UTC) Received: (qmail 68666 invoked by uid 500); 27 Feb 2012 16:14:31 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 68621 invoked by uid 500); 27 Feb 2012 16:14: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 68612 invoked by uid 99); 27 Feb 2012 16:14:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Feb 2012 16:14:31 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of saint.ack@gmail.com designates 209.85.214.169 as permitted sender) Received: from [209.85.214.169] (HELO mail-tul01m020-f169.google.com) (209.85.214.169) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Feb 2012 16:14:25 +0000 Received: by obbta7 with SMTP id ta7so7321166obb.14 for ; Mon, 27 Feb 2012 08:14:04 -0800 (PST) Received-SPF: pass (google.com: domain of saint.ack@gmail.com designates 10.182.14.97 as permitted sender) client-ip=10.182.14.97; Authentication-Results: mr.google.com; spf=pass (google.com: domain of saint.ack@gmail.com designates 10.182.14.97 as permitted sender) smtp.mail=saint.ack@gmail.com; dkim=pass header.i=saint.ack@gmail.com Received: from mr.google.com ([10.182.14.97]) by 10.182.14.97 with SMTP id o1mr5069315obc.57.1330359244561 (num_hops = 1); Mon, 27 Feb 2012 08:14:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=5z1Kbis3Zv3QB9C51HCav+SmkXBcRZ86Xwvp5Kca4LY=; b=nSHvvoXNaO4fnopmkxDJHB/0xueiEbMF9LtDVsZrOv5nCG3iJFTFxMSyilHfDTOf/Z 3PKg/n2zguAI28x7kOQefcURKwl7odb14gHO2xDRo9ZCJ9N1RwLO/VjrMJVu8nZnimib /xQInxgmV01oah2q+W1JO3G/FNaVm3R008L3g= MIME-Version: 1.0 Received: by 10.182.14.97 with SMTP id o1mr4547664obc.57.1330359244523; Mon, 27 Feb 2012 08:14:04 -0800 (PST) Sender: saint.ack@gmail.com Received: by 10.182.70.132 with HTTP; Mon, 27 Feb 2012 08:14:04 -0800 (PST) In-Reply-To: References: Date: Mon, 27 Feb 2012 08:14:04 -0800 X-Google-Sender-Auth: Zuql8Bda0Yf7wvzgbYW0MHGOXHU Message-ID: Subject: Re: Bytes in hbase thrift api From: Stack To: user@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 On Mon, Feb 27, 2012 at 2:52 AM, Dalia Sobhy wrote: > Can anyone provide me with type of bytes used with hbase thrift api.. > They have no type. They are just bytes. What is your issue? What is failing? St.Ack