hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-901) Add a limit to key length, check key and value length on client side.
Date Thu, 25 Sep 2008 17:09:44 GMT

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

stack commented on HBASE-901:
-----------------------------

Why need an upper-bound on key length?  What are we afraid of?  100M keys?

Why does it have to be configurable?  Why not explicit config in hbase-site?  Or am I missing
something?

> 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.


Mime
View raw message