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

Enis Soztutar commented on HBASE-6818:
--------------------------------------

This is a hard one to tackle, since the META table's name is all over the code 
base. It is not straight, or even sensible, to change the name of the META 
table. Instead, we can work on a solution that changes the file name of the 
META table at the file system level, if the underlying filesystem is local (and 
windows). we also have to standardize on the local file name of the META table, 
so that we dont allow user level tables of that name.
                
> [WINDOWS] Catalog table .META. violates the naming convention in Window OS
> --------------------------------------------------------------------------
>
>                 Key: HBASE-6818
>                 URL: https://issues.apache.org/jira/browse/HBASE-6818
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 0.96.0, 0.94.3
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>              Labels: windows
>
> There are two catalog tables in HBase, ROOT and .META., whose representitives 
> in Windows file system are folders. However, the name of .META. table 
> violates the naming convention in Windows, as Windows doesn't support any 
> file/directory whose name ending with a period '.'.
> The following are the related description from msdn.microsoft.com for naming 
> convention for Windows :
> Do not end a file or directory name with a space or a period. Although the 
> underlying file system may support such names, the Windows shell and user 
> interface does not. However, it is acceptable to specify a period as the 
> first character of a name. For example, ".temp".
> Note that this does not affect hdfs, but only RawLocalFileSystem, and 
> single-node local hbase clusters.  

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

Reply via email to