Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9425E106BD for ; Fri, 21 Jun 2013 10:09:23 +0000 (UTC) Received: (qmail 84824 invoked by uid 500); 21 Jun 2013 10:09:23 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 84554 invoked by uid 500); 21 Jun 2013 10:09:22 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 84537 invoked by uid 99); 21 Jun 2013 10:09:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Jun 2013 10:09:20 +0000 Date: Fri, 21 Jun 2013 10:09:20 +0000 (UTC) From: "Hamed Madani (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-8782) Thrift2 can not parse values when using framed transport MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-8782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690170#comment-13690170 ] Hamed Madani commented on HBASE-8782: ------------------------------------- Thank you Ted. I'm not sure what you like me to do. Below is what I get *Without this patch* running thrift2 in nonblocking mode (trying to scan "my_table" (framed transport)) {code} org.apache.hadoop.hbase.exceptions.TableNotFoundException: Cannot find row in .META. for table: ? openScanner my_table @ @ row=\xFF\xBF\xBD\x01\xF0\xF1\x00\x00\xF0\x0BopenScanner\x00\x00\(..many more) at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:137) at org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:102) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:857) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:917) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:809) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:778) at org.apache.hadoop.hbase.client.HTable.finishSetup(HTable.java:245) at org.apache.hadoop.hbase.client.HTable.(HTable.java:186) at org.apache.hadoop.hbase.client.HTableFactory.createHTableInterface(HTableFactory.java:39) at org.apache.hadoop.hbase.client.HTablePool.createHTable(HTablePool.java:270) at org.apache.hadoop.hbase.client.HTablePool.findOrCreateTable(HTablePool.java:200) at org.apache.hadoop.hbase.client.HTablePool.getTable(HTablePool.java:179) at org.apache.hadoop.hbase.client.HTablePool.getTable(HTablePool.java:218) at org.apache.hadoop.hbase.thrift2.ThriftHBaseServiceHandler.getTable(ThriftHBaseServiceHandler.java:127) at org.apache.hadoop.hbase.thrift2.ThriftHBaseServiceHandler.openScanner(ThriftHBaseServiceHandler.java:306) {code} > Thrift2 can not parse values when using framed transport > -------------------------------------------------------- > > Key: HBASE-8782 > URL: https://issues.apache.org/jira/browse/HBASE-8782 > Project: HBase > Issue Type: Bug > Components: Thrift > Affects Versions: 0.95.1 > Reporter: Hamed Madani > Attachments: HBASE_8782.patch > > > ThriftHBaseServiceHandler.java use .array() on table names , and values (family , qualifier in checkandDelete , etc) which resulted in incorrect values with framed transport. Replacing .array() with getBytes() fixed this problem. I've attached the patch > EDIT: updated the patch to cover checkAndPut(), checkAndDelete() -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira