accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3197) Remove deprecated API cruft
Date Fri, 10 Oct 2014 23:32:34 GMT

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

Josh Elser commented on ACCUMULO-3197:
--------------------------------------

As part of the removal of the confusing Accumulo configuration story, can you please make
a point to be clear at the javadoc level about what API methods do exist and how they should
be used?

Given that I'm always confused about what methods I can actually use (albeit some of my confusion
is related to the server-side AccumuloConfiguration methods), I imagine users are equally
or more confused :)

> Remove deprecated API cruft
> ---------------------------
>
>                 Key: ACCUMULO-3197
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3197
>             Project: Accumulo
>          Issue Type: Task
>          Components: client
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>              Labels: api
>             Fix For: 1.7.0
>
>
> Deprecated stuff should be removed from the API. I'm okay with moving away from some
of this in a 1.7.0 release, especially because it will clean up the confusing instance.getConfiguration
stuff, but if there's a strong objection, we can wait until 2.0.0 instead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message