[ACCUMULO-477] inconsistent names and duplicate methods in IteratorSettings

• Type: Improvement
• Status: Resolved
• Priority: Trivial
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Component/s: client
• Assignee: Eric C. Newton
• Reporter: David Medinets
• Created: 20/Mar/12 17:34
• Updated: 25/Apr/14 18:58
• Resolved: 21/Mar/12 21:36

Description

David Medinets noticed

A Property object used to hold key-value information used to modify
the behavior of an Interator. However, these are the methods
available:

 getProperties
 setProperties
 hasProperties
 addOption
 removeOption
 addOptions
 clearOptions

Is there a reason why the same concept as two names? I'd like to
settle on one name and standardise.

Could we change the names to be something like
getInteratorSettingProperties? I know that some people are annoyed by
longer method names, but when searching through a code base, have
unique names is handy. Searching for a generically named method - such
as getProperties, returns a lot of false positives.