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-1516) Clean up Constants
Date Tue, 11 Mar 2014 21:04:51 GMT

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

Christopher Tubbs commented on ACCUMULO-1516:
---------------------------------------------

bq. Might it make sense to move that out to other files as well ... ?

Yes, I think so, in a separate JIRA, as you say. That stuff might be best in a ZK abstraction
layer. Perhaps as part of the CURATOR work (if that pans out in the future), or the some other
metadata management layer. Personally, I'd prefer any Constants be scoped to the layer they
apply to, and not simply into a separate arbitrary Constants file.

> Clean up Constants
> ------------------
>
>                 Key: ACCUMULO-1516
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1516
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: client, master, tserver
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>            Priority: Minor
>             Fix For: 1.6.0
>
>
> o.a.a.core.Constants has become a mess, full of both useful and not useful stuff that
is difficult to sift through.
> For instance, there's a String literal constant for "UTF-8" that is only ever used in
one place, and Constants.NO_AUTHS should really be Authorizations.EMPTY
> Some of this, I want/need to clean up so I can track down all the important bits to migrate
the root tablet to its own table without clutter.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message