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] [Created] (ACCUMULO-1025) Don't deprecate AuthInfo
Date Sun, 03 Feb 2013 01:11:11 GMT
Christopher Tubbs created ACCUMULO-1025:
-------------------------------------------

             Summary: Don't deprecate AuthInfo
                 Key: ACCUMULO-1025
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1025
             Project: Accumulo
          Issue Type: Sub-task
            Reporter: Christopher Tubbs


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 itself.

--
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: http://www.atlassian.com/software/jira

Mime
View raw message