[
https://issues.apache.org/jira/browse/ACCUMULO-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs updated ACCUMULO-477:
---------------------------------------
Summary: inconsistent names and duplicate methods in IteratorSettings
(was: inconsistent names and duplicate methods in IteratorSettings )
> inconsistent names and duplicate methods in IteratorSettings
> ------------------------------------------------------------
>
> Key: ACCUMULO-477
> URL: https://issues.apache.org/jira/browse/ACCUMULO-477
> Project: Accumulo
> Issue Type: Improvement
> Components: client
> Reporter: David Medinets
> Assignee: Eric Newton
> Priority: Trivial
> Fix For: 1.4.0
>
>
> David Medinets noticed
> {quote}
> A Property object used to hold key-value information used to modify
> the behavior of an Interator. However, these are the methods
> available:
> {noformat}
> getProperties
> setProperties
> hasProperties
> addOption
> removeOption
> addOptions
> clearOptions
> {noformat}
> 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.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
