accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1025) Don't deprecate AuthInfo
Date Thu, 28 Feb 2013 18:01:17 GMT


Hudson commented on ACCUMULO-1025:

Integrated in Accumulo-Trunk #749 (See [])
    ACCUMULO-1025 - deprecating AuthInfo properly (Revision 1451250)

     Result = SUCCESS
vines : 
Files : 
* /accumulo/trunk
* /accumulo/trunk/core
* /accumulo/trunk/core/src/main/java/org/apache/accumulo/core/security/thrift/
* /accumulo/trunk/core/src/main/thrift/security.thrift

> Don't deprecate AuthInfo
> ------------------------
>                 Key: ACCUMULO-1025
>                 URL:
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: master, tserver
>            Reporter: Christopher Tubbs
>            Assignee: John Vines
>             Fix For: 1.5.0
> AuthInfo, even if no longer used, needs to remain in the thrift build, in case there
are thrift code generation bugs identified and fixed in future 1.5.x releases. The way AuthInfo
was deprecated (the class was removed from the thrift generation, and a deprecation tag was
added to the class itself) means that any such fixes will not be applied to AuthInfo.
> Instead, if this object is not intended to be used in the public API (which it isn't,
because it's for internal serialization for RPC calls, like all the thrift objects in core),
the places where it is exposed to the public API need to be deprecated, not the AuthInfo class

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message