[
https://issues.apache.org/jira/browse/ACCUMULO-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065246#comment-14065246
]
Josh Elser commented on ACCUMULO-3004:
--------------------------------------
Additionally, this only happens on the connector and instance. You can merrily
set the tableName, iterators, offline scanners, etc as many times as desired.
I imagine this was done because of the differences in how this data is
serialized within the configuration (similar to ACCUMULO-3001), but there has
to be something better that can be done.
> Remove thrown Exceptions when Instance and/or Connector are set multiple
> times on InputFormat
> ---------------------------------------------------------------------------------------------
>
> Key: ACCUMULO-3004
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3004
> Project: Accumulo
> Issue Type: Improvement
> Affects Versions: 1.5.1, 1.6.0
> Reporter: Josh Elser
> Fix For: 1.7.0
>
>
> If a user happens to set the Connector for Instance information on the same
> Configuration object multiple times, they get slammed with an
> IllegalArgumentException.
> These setters should be idempotent and having them invoked with the same data
> multiple times should not change the serialized form in the Configuration.
> Tentatively marked for 1.7.0 as its a change in how 1.5 and 1.6 currently
> operate.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
