Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1420237168.1222363304308.JavaMail.jira@brutus>
Date: Thu, 25 Sep 2008 10:21:44 -0700 (PDT)
From: "Jim Kellerman (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-901) Add a limit to key length, check key
 and value length on client side.
In-Reply-To: <466380840.1222362224342.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634552#action_12634552 ] 

Jim Kellerman commented on HBASE-901:
-------------------------------------

Jean-Daniel points out that we still need to get to the HTableDescriptor, because even if key lengths have a fixed maximum, value lengths are configurable.

> Add a limit to key length, check key and value length on client side.
> ---------------------------------------------------------------------
>
>                 Key: HBASE-901
>                 URL: https://issues.apache.org/jira/browse/HBASE-901
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: client
>            Reporter: Jim Kellerman
>            Assignee: Jean-Daniel Cryans
>            Priority: Blocker
>             Fix For: 0.19.0
>
>
> Currently there is no limit on key length and there should be. It should be a parameter in HTableDescriptor since the row key length needs to be considered in addition to the column key.
> It should be trivial to add, since HTD can be upgraded without requiring a migration.
> Checking of the key length (and the value length) should be done on the client side as it will fail early rather than once the request is sent to the server.
> This means that a BatchUpdate needs a reference to either the HTable or to the HTD. It can be a transient reference so that the HTable (or HTD) need not be serialized/deserialized.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.