You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org> on 2011/08/08 19:56:27 UTC
[jira] [Commented] (MAPREDUCE-2780) Standardize the value of token
service
[ https://issues.apache.org/jira/browse/MAPREDUCE-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081091#comment-13081091 ]
Jitendra Nath Pandey commented on MAPREDUCE-2780:
-------------------------------------------------
I see only one issue with changing the setService API to take InetSocketAddress. It forces to set ip/host/port in the service. If we later decide to store something else in the service for example, uri with scheme, we will have to change it again.
I would recommend to keep setService API unchanged, however a utility method in SecurityUtil to construct DT service from a socket address is good.
> Standardize the value of token service
> --------------------------------------
>
> Key: MAPREDUCE-2780
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2780
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Fix For: 0.20.205.0
>
> Attachments: MAPREDUCE-2780-2.patch, MAPREDUCE-2780.patch
>
>
> The token's service field must (currently) be set to "ip:port". All the producers of a token are independently building the service string. This should be done via a common method to reduce the chance of error, and to facilitate the field value being easily changed in the (near) future.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira