hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars George (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-1995) Add configurable max value size check
Date Sat, 28 Nov 2009 22:07:20 GMT

     [ https://issues.apache.org/jira/browse/HBASE-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lars George updated HBASE-1995:
-------------------------------

    Attachment: HBASE-1995.patch

Patch adds check for configurable maximum KeyValue length on the client side. By default it
is disabled (or should we set a reasonable maximum?) and client unit test has specific test
added and passes.

> Add configurable max value size check
> -------------------------------------
>
>                 Key: HBASE-1995
>                 URL: https://issues.apache.org/jira/browse/HBASE-1995
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: client
>            Reporter: Lars George
>            Assignee: Lars George
>            Priority: Minor
>             Fix For: 0.21.0
>
>         Attachments: HBASE-1995.patch
>
>
> After discussing with Michael, the issue was that if you have a region size of for example
256M and you add a 1G value into a column then that region cannot split and a cluster can
become lopsided. It also means that you have a really large block and the memstore would need
to handle the 1G data. I proposed to add a configurable upper boundary check that is throwing
an exception on the client side if the user tries to add a value larger than that limit. Ideally
it would be set to the maximum region size or less. 

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