[
https://issues.apache.org/jira/browse/HADOOP-13123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277421#comment-15277421
]
Allen Wittenauer commented on HADOOP-13123:
-------------------------------------------
I don't think adding a config flag is the proper fix.
That stack trace indicates that the application has bundled an older version of
the security classes rather than using the ones on the Hadoop provided
classpath. I haven't looked, but I'm fairly certain they are a) not public APIs
and b) there is no guarantee around stability of the files. Frankly, any app
that does this is begging to be broken by changes and deserves to die a fiery
death.
Additionally, if that is not the problem, then HADOOP-12563 should get pulled
from branch-2. trunk is expected to make incompatible changes that may break
pre-existing applications. There should be no reasonable expectation that an
incompatible release would use a deprecated format by default at all.
> Permit the default hadoop delegation token file format to be configurable
> -------------------------------------------------------------------------
>
> Key: HADOOP-13123
> URL: https://issues.apache.org/jira/browse/HADOOP-13123
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Matthew Paduano
> Assignee: Matthew Paduano
>
> If one environment updates to using the new dtutil code and accompanying
> Credentials code, there is a backward compatibility issue with the default
> file format being JAVA. Older clients need to be updated to ask for a file
> in the legacy format (FORMAT_JAVA).
> As an aid to users in this trap, we can add a configuration property to set
> the default file format. When set to FORMAT_JAVA, the new server code will
> serve up legacy files without being asked. The default value for this
> property will remain FORMAT_PB. But affected users can add this config
> option to the services using the newer code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
