[
https://issues.apache.org/jira/browse/HADOOP-15704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619086#comment-16619086
]
Steve Loughran commented on HADOOP-15704:
-----------------------------------------
I think we can move this under the phase II stuff, but for branch-3.2 I'd like
the APIs to be marked as
{code}
@InterfaceAudience.LimitedPrivate("authorization-subsystems")
@InterfaceStability.Unstable
{code}
Why? it explicitly makes clear that this has less stability than public &
evolving, and that it's for a specific purpose. If
org.apache.hadoop.fs.azurebfs.auth package of HADOOP-15273 adds the same tag
(and the stuff in HADOOP-15446) then there's a specific declared use of these
entry points which sets up expectations: this stuff isn't for broad use
we've done something similar with management tooling in the past, to say "this
is only for management tools which are expected to track changes if/when they
happen"
> ABFS: Consider passing FS URI to CustomDelegationTokenManager
> -------------------------------------------------------------
>
> Key: HADOOP-15704
> URL: https://issues.apache.org/jira/browse/HADOOP-15704
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Reporter: Thomas Marquardt
> Assignee: Da Zhou
> Priority: Major
>
> Refer to Steve's comments in HADOOP-15692. Passing the FS or FS URI to the
> CustomDelegationTokenManager would allow it to provide per-filesystem tokens.
> We currently have implementations of CustomDelegationTokenManager, and need
> to do a little leg work here, but it may be possible to update before GA.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
