accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Miller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-4662) Fix ambiguous table references
Date Fri, 01 Sep 2017 17:15:00 GMT

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

Michael Miller commented on ACCUMULO-4662:
------------------------------------------

After ACCUMULO-4699 is fixed, refactoring of String -> Table.ID for sourceTableId in SequentialWorkAssigner
will need to be done.  

> Fix ambiguous table references
> ------------------------------
>
>                 Key: ACCUMULO-4662
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4662
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Michael Miller
>            Assignee: Michael Miller
>             Fix For: 1.7.4, 1.8.2, 2.0.0
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> While working on ACCUMULO-3238, I noticed a few places where we use the ambiguous variable:

> {code}String table{code}  
> This is problematic since it is not clear what the variable is actually referring to.
 It can be referring to either a tableId or tableName both of which are Strings but different
in values Zookeeper.  Typically the actual value of the variable can be derived from surrounding
code but this is not always the case. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message