adoroszlai commented on pull request #3259:
URL: https://github.com/apache/ozone/pull/3259#issuecomment-1084638669


   > Ozone Token Renewer's are implemented in 
[BasicOzoneClientAdapterImpl.java#L401](https://github.com/apache/ozone/blob/master/hadoop-ozone/ozonefs-common/src/main/java/org/apache/hadoop/fs/ozone/BasicOzoneClientAdapterImpl.java#L401)
 and 
[BasicRootedOzoneClientAdapterImpl.java#L830](https://github.com/apache/ozone/blob/master/hadoop-ozone/ozonefs-common/src/main/java/org/apache/hadoop/fs/ozone/BasicRootedOzoneClientAdapterImpl.java#L830)
 , which are not present in the ozone-filesystem-hadoop3-*.jar fat jar.
   
   Can you please explain why you think these are not present?  I see them in 
both 1.2.0 release:
   
   ```
   unzip -t ozone-1.2.0/share/ozone/lib/ozone-filesystem-hadoop3-1.2.0.jar | 
grep Renewer
       testing: 
org/apache/hadoop/hdds/security/token/OzoneBlockTokenIdentifier$Renewer.class   
OK
       testing: 
org/apache/hadoop/fs/ozone/BasicRootedOzoneClientAdapterImpl$Renewer.class   OK
       testing: 
org/apache/hadoop/fs/ozone/BasicOzoneClientAdapterImpl$Renewer.class   OK
   ```
   
   and in current `master`:
   
   ```
   unzip -t 
hadoop-ozone/dist/target/ozone-1.3.0-SNAPSHOT/share/ozone/lib/ozone-filesystem-hadoop3-1.3.0-SNAPSHOT.jar
 | grep Renewer
       testing: 
org/apache/hadoop/hdds/security/token/OzoneBlockTokenIdentifier$Renewer.class   
OK
       testing: 
org/apache/hadoop/fs/ozone/BasicRootedOzoneClientAdapterImpl$Renewer.class   OK
       testing: 
org/apache/hadoop/fs/ozone/BasicOzoneClientAdapterImpl$Renewer.class   OK
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



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

Reply via email to