accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1704) IteratorSetting missing (int,String,Class,Map) constructor
Date Thu, 10 Oct 2013 00:07:42 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791021#comment-13791021
] 

Christopher Tubbs commented on ACCUMULO-1704:
---------------------------------------------

Two reasons not to do this (and mitigating thoughts):

# Too many methods to maintain (but this is alleviated by the fact that it is functionally
identical, as you say).
# Make it clear that we're storing configuration of the class name when it gets sent over
the wire. We're not transmitting the class. If the class doesn't exist on the other side,
it won't work (but this could be alleviated with good javadocs, perhaps).


> IteratorSetting missing (int,String,Class,Map) constructor
> ----------------------------------------------------------
>
>                 Key: ACCUMULO-1704
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1704
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.5.0
>            Reporter: Mike Drob
>            Priority: Trivial
>              Labels: newbie
>             Fix For: 1.5.1, 1.6.0
>
>
> org.apache.accumulo.core.client.IteratorSetting has several constructors including one
for {{(int, String, String, Map)}}, where the third argument is a class name, but is missing
one that takes {{(int, String, Class, Map)}}. This would be useful for users since it would
be functionally identical to the other 4 argument constructor, and we already have some that
take {{Class}} objects instead of {{String}} class names.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message