[ACCUMULO-4662] Fix ambiguous table references

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.0
• Assignee: Michael Miller
• Reporter: Michael Miller
• Created: 21/Jun/17 16:16
• Updated: 07/Sep/17 15:43
• Resolved: 07/Sep/17 15:43

Description

While working on ACCUMULO-3238, I noticed a few places where we use the ambiguous variable:

String table

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.

Issue Links

• depends upon: ACCUMULO-4699 Map in SequentialWorkAssigner uses two different keys
• relates to: ACCUMULO-3238 Replace String tableName arguments with TableHandle