You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Michael Miller (JIRA)" <ji...@apache.org> on 2017/06/21 16:56:00 UTC

[jira] [Updated] (ACCUMULO-4662) Fix ambiguous table references

     [ https://issues.apache.org/jira/browse/ACCUMULO-4662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Miller updated ACCUMULO-4662:
-------------------------------------
    Fix Version/s: 2.0.0
                   1.8.2
                   1.7.4

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