[ 
https://issues.apache.org/jira/browse/HADOOP-16277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Venkatesh Sridharan updated HADOOP-16277:
-----------------------------------------
    Description: It would be nice to have a getTokenKind() method exposed in 
[FileSystem|[https://github.com/apache/hadoop-common/blob/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/FileSystem.java]]
 . Currently WebHdfsFileSystem class has getTokenKind() which is protected. 
Having it in FileSystem makes it easier to use at runtime when the consumer 
doesn't know what the underlying FileSystem implementation is.   (was: It would 
be nice to have a getTokenKind() method exposed in 
[FileSystem|[https://github.com/apache/hadoop-common/blob/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/FileSystem.java]]
 . Currently WebHdfsFileSystem class has getTokenKind() which is protected. 
Having it in FileSystem makes it easier to use at runtime when the consumer 
doesn't know what the FileSystem implementation is. )

> Expose getTokenKind method in FileSystem
> ----------------------------------------
>
>                 Key: HADOOP-16277
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16277
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Venkatesh Sridharan
>            Priority: Trivial
>
> It would be nice to have a getTokenKind() method exposed in 
> [FileSystem|[https://github.com/apache/hadoop-common/blob/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/FileSystem.java]]
>  . Currently WebHdfsFileSystem class has getTokenKind() which is protected. 
> Having it in FileSystem makes it easier to use at runtime when the consumer 
> doesn't know what the underlying FileSystem implementation is. 



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