[
https://issues.apache.org/jira/browse/HADOOP-15336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16419272#comment-16419272
]
Íñigo Goiri commented on HADOOP-15336:
--------------------------------------
{quote}
In the above stack trace, router is decoding response from namenode not
request. So it doesn't need to decode.
{quote}
My example applies in the opposite direction.
When we get /data/user1 from the NN, we need to translate it back into
/user/user1.
Note that this is the simple example, we have a bunch of operations that we
also need to aggregate across all subclusters.
{quote}
The backwards incompatible flag on this jira means HADOOP-14104 introduced this
incompatibility and that is not correct. I wasn't clear earlier.
{quote}
Not sure who added the incompatibility but there is one here. In any case, we
should remove the label and for sure not mark it as such.
{quote}
You can't reproduce this issue if there are only 2 components.
{quote}
Correct, you need three components.
In any case, I think this is worth committing.
> NPE for FsServerDefaults.getKeyProviderUri() for clientProtocol communication
> between 2.7 and 3.2
> -------------------------------------------------------------------------------------------------
>
> Key: HADOOP-15336
> URL: https://issues.apache.org/jira/browse/HADOOP-15336
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 3.1.0, 3.2.0
> Reporter: Sherwood Zheng
> Assignee: Sherwood Zheng
> Priority: Major
> Labels: backward-incompatible, common
> Attachments: HADOOP-15336.000.patch, HADOOP-15336.001.patch
>
>
> KeyProviderUri is not available in 2.7 so when 2.7 clients contact with 3.2
> services, it cannot find the key provider URI and triggers a
> NullPointerException.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
