You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2014/10/11 01:28:33 UTC

[jira] [Commented] (ACCUMULO-3197) Remove deprecated API cruft

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

Christopher Tubbs commented on ACCUMULO-3197:
---------------------------------------------

So, the result of the deprecation discussions on the mailing lists is that people would prefer to be more conservative about removing deprecated APIs in general. So, that rules out many of the deprecations I was thinking about doing. However, it was identified that there may be certain exceptions, where good reasons might warrant removal on a case-by-case basis. In the future, this might warrant a bigger version bump, but for 1.x, I think the Instance.getConfiguration stuff is sufficiently problematic to warrant removal in 1.7.0, and there were no outstanding objections on the thread, so I'll proceed with that and leave the removal of the rest of the deprecated stuff to 2.0.0.

> 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)