[
https://issues.apache.org/jira/browse/ACCUMULO-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13871557#comment-13871557
]
Christopher Tubbs commented on ACCUMULO-1963:
---------------------------------------------
Well, it can't be *anything*... we still want to make sure to avoid collisions
with non-reserved (user) tables' IDs, which are base36 decimals. Additionally,
for sanity reasons, I think it should differ by more than just case (especially
if we want sane behavior on case-insensitive filesystems like HFS+ on OS X).
Personally, I like it sorting before other tables in the underlying filesystem,
for convenience when I do directory listings... but it doesn't have to.
> Rename metadata table ID (!0) so it doesn't have an exclamation point
> ---------------------------------------------------------------------
>
> Key: ACCUMULO-1963
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1963
> Project: Accumulo
> Issue Type: Bug
> Reporter: Christopher Tubbs
> Fix For: 1.7.0
>
>
> The table ID for the metadata table is problematic. The reserved character
> requires special escaping in shells, like bash.
> This was going to happen with ACCUMULO-1712, but would require some effort to
> upgrade and test the root table, walogs, and HDFS paths, so this is going to
> be postponed and not completed for 1.6.
> The proposed new table ID is "\+m", following the conventions of the root
> table, whose ID is "\+r". ("\+" can be used much more safely across
> filesystems and shells).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
