You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2013/03/14 00:38:14 UTC

[jira] [Commented] (HBASE-8093) Change the .META. table name for file system incompatibility

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

stack commented on HBASE-8093:
------------------------------

+1 as long as you can make the alias work.

Why call it something wah like -META-?  We have the notion of 'system tables' now...  We should name them w/ same convention if possible.  I suppose there is _acl_ which would fit this category.  What tables did Jesse add if any in his patch?  System tables being with a dot?
                
> Change the .META. table name for file system incompatibility
> ------------------------------------------------------------
>
>                 Key: HBASE-8093
>                 URL: https://issues.apache.org/jira/browse/HBASE-8093
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, Region Assignment, regionserver
>    Affects Versions: 0.95.0, 0.98.0
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: 0.95.0, 0.98.0
>
>
> Having a table named ".META." causes problems on NTFS file system under windows, since it does not allow file names ending with ".". 
> Nicolas and I have been thinking of just changing the name of the META to be {noformat}-META-{noformat}
> Since 0.96 is the singularity, and we already moved ROOT to zk, now seems like a good time to do such a change. There will be no rolling upgrade support. 
> We can migrate META, and can keep BC, by having an internal alias between the old meta name, and new meta name. This way, outside scripts and code who reads META can still work. 
> See also HBASE-6818, HBASE-6821.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira