[
https://issues.apache.org/jira/browse/HBASE-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260719#comment-13260719
]
Hudson commented on HBASE-5848:
-------------------------------
Integrated in HBase-0.94 #143 (See
[https://builds.apache.org/job/HBase-0.94/143/])
HBASE-5848 Create table with EMPTY_START_ROW passed as splitKey causes the
HMaster to abort (Ram) (Revision 1329827)
Result = FAILURE
ramkrishna :
Files :
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/client/TestAdmin.java
> Create table with EMPTY_START_ROW passed as splitKey causes the HMaster to
> abort
> --------------------------------------------------------------------------------
>
> Key: HBASE-5848
> URL: https://issues.apache.org/jira/browse/HBASE-5848
> Project: HBase
> Issue Type: Bug
> Components: client
> Reporter: Lars Hofhansl
> Assignee: ramkrishna.s.vasudevan
> Priority: Minor
> Fix For: 0.94.0, 0.96.0
>
> Attachments: HBASE-5848.patch, HBASE-5848.patch, HBASE-5848_0.94.patch
>
>
> A coworker of mine just had this scenario. It does not make sense the
> EMPTY_START_ROW as splitKey (since the region with the empty start key is
> implicit), but it should not cause the HMaster to abort.
> The abort happens because it tries to bulk assign the same region twice and
> then runs into race conditions with ZK.
> The same would (presumably) happen when two identical split keys are passed,
> but the client blocks that. The simplest solution here is to also block
> passed null or EMPTY_START_ROW as split key by the client.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
