hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David S. Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6158) Data loss if the words 'merges' or 'splits' are used as Column Family name
Date Sat, 23 Jun 2012 13:22:42 GMT

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

David S. Wang commented on HBASE-6158:

This change does make upgrade scripts more complex as noted earlier in this JIRA.  Having
to change the scripts to detect this condition is potentially problematic: if "splits" or
"merges" was an actual user table before the upgrade, what does the script do in that case?

Also, is "merges"/MERGEDIR actually created anywhere?  I don't see any such call in the code
in trunk or in earlier releases.
> Data loss if the words 'merges' or 'splits' are used as Column Family name
> --------------------------------------------------------------------------
>                 Key: HBASE-6158
>                 URL: https://issues.apache.org/jira/browse/HBASE-6158
>             Project: HBase
>          Issue Type: Bug
>          Components: master, regionserver
>    Affects Versions: 0.94.0
>            Reporter: Aditya Kishore
>            Assignee: Aditya Kishore
>             Fix For: 0.92.2, 0.94.1
>         Attachments: HBASE-6158_94.patch, HBASE-6158_trunk.patch
> If a table is creates with either 'merges' or 'splits' as one of the Column Family name
it can never be flushed to the disk even though the table creation (and data population) succeeds.
> The reason for this is that these two are used as temporary directory names inside the
region folder or merge and splits respectively and hence conflicts with the directories created
for CF with same name.
> A simple fix would be to uses ".merges' and ".splits" as the working folder (patch attached).
This will also be consistent with other work folder names. An alternate fix would be to declare
these words (and other similar) as reserve words and throw exception when they are used. However,
I do find the alternate approach as unnecessarily restrictive.

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


View raw message