accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-4662) Fix ambiguous table references
Date Wed, 06 Sep 2017 23:20:00 GMT


Christopher Tubbs commented on ACCUMULO-4662:

I see some commits against this. Are there more expected, or can this be closed?

> Fix ambiguous table references
> ------------------------------
>                 Key: ACCUMULO-4662
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Michael Miller
>            Assignee: Michael Miller
>             Fix For: 2.0.0
>          Time Spent: 1h 10m
>  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

View raw message