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

Hudson commented on HDDS-945:
-----------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #15791 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/15791/])
HDDS-945. Fix generics warnings in delegation token. Contributed by Ajay (xyao: 
rev 8978466fca92b035131f87c3e1c0e60ae741c339)
* (edit) 
hadoop-ozone/common/src/main/java/org/apache/hadoop/ozone/security/OzoneDelegationTokenSecretManager.java
* (edit) 
hadoop-ozone/common/src/test/java/org/apache/hadoop/ozone/security/TestOzoneDelegationTokenSecretManager.java
* (edit) 
hadoop-ozone/common/src/main/java/org/apache/hadoop/ozone/security/OzoneSecretStore.java
* (edit) 
hadoop-ozone/integration-test/src/test/java/org/apache/hadoop/ozone/client/rpc/TestOzoneRpcClient.java
* (edit) 
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/OzoneManager.java


> Fix generics warnings in delegation token
> -----------------------------------------
>
>                 Key: HDDS-945
>                 URL: https://issues.apache.org/jira/browse/HDDS-945
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Ajay Kumar
>            Assignee: Ajay Kumar
>            Priority: Major
>             Fix For: 0.4.0
>
>         Attachments: HDDS-945-HDDS-4.00.patch, HDDS-945-HDDS-4.01.patch
>
>
> There are warnings in genrics related code in 
> {{OzoneDelegationTokenSecretManager}} and {{OzoneSecretStore}}. Since we 
> already have base class which can be used for other kind of identifiers we 
> can remove this generics related code as fixing it will make it bit more 
> complicated (also looks unnecessary for current use cases)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to