accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2318) Renaming table don't require namespace
Date Thu, 06 Feb 2014 02:42:12 GMT

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

Christopher Tubbs commented on ACCUMULO-2318:
---------------------------------------------

The principle for the previous behavior, prior to this ticket, was, by analogy that "Rename
Christopher Tubbs to Michael" was intuitive enough, and that one shouldn't have to say "Rename
Christopher Tubbs to Michael Tubbs". Likewise, the first parameter could be fully-qualified,
because it needed enough information to identify the table to change, and the second parameter
was simply the new name to give the identified table (not a new location/namespace... simply
a new name).

I feel it's non-intuitive that a rename doesn't just update the name of the table, but might
also move it. By expecting unqualified names, it's clear that this behavior is not possible,
but we also allowed fully-qualified names, as long as it was referring to the same namespace,
so users weren't surprised if they always used fully-qualified names.

So, I'm not convinced this was any more intuitive than the documented behavior, but I'm not
strongly tied to either one, as far as intuitive-ness. However, it was made quite clear in
the javadoc how it was expected to work, and the previous implementation followed the documented
behavior. It now no longer does. If this change is acceptable, then it needs a corresponding
javadoc update.


> Renaming table don't require namespace
> --------------------------------------
>
>                 Key: ACCUMULO-2318
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2318
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>            Reporter: John Vines
>            Assignee: John Vines
>             Fix For: 1.6.0
>
>
> If you rename a table, the old table name must be fully qualified. But the destination
table does not require the namespace prefix. First of all, this doesn't seem intuitive. Secondly,
it will makes things monumentally difficult should we support renaming across namespaces.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message