[
https://issues.apache.org/jira/browse/ACCUMULO-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs resolved ACCUMULO-3755.
-----------------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 1.6.3)
Closing this as "Won't Fix".
There's not much we can really do about this, because:
* It's already fixed in 1.7.0 and later
* We can't change the API in 1.6.x to fix anything anyway. We can't even
deprecate stuff without adding replacements, and we can't do that in 1.6.x
(semver).
* The best we can do is list all the extra classes that should have been
declared public API... but that's not *that* helpful, especially since affected
users will already be aware from the fact that they are parameters / return
types to methods already in the declared public API. It could also introduce
problems, because breaking changes in some of these classes may have already
violated semver going to 1.7.0. So, declaring these classes would add
guarantees about them that we cannot achieve (because 1.7.0 is already
released).
* We could just add an apology to the README and point users to 1.7.0 and
later, but that's not really helpful for users upgrading to newer 1.6.x
versions because they're sticking with 1.6. It also doesn't really provide any
new information to users.
* My understanding is that [~kturner] doesn't have time to finish this at the
moment, so it's not worth holding up a 1.6.3 release. (I'm sure he'll chime in
if/when he can, if he thinks he can do it).
In summary, I don't think we can/should do anything about this for 1.6.
> Update 1.6 API statement
> ------------------------
>
> Key: ACCUMULO-3755
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3755
> Project: Accumulo
> Issue Type: Bug
> Reporter: Keith Turner
> Assignee: Keith Turner
> Priority: Blocker
>
> A lot of changes were made in ACCUMULO-3657 for 1.7.0 to simplify and clarify
> the Accumulo API statement. The 1.6 API statement still does not include all
> of the classes that user would realistically have to use.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)