[
https://issues.apache.org/jira/browse/MAPREDUCE-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756346#action_12756346
]
Vinod K V commented on MAPREDUCE-990:
-------------------------------------
bq. Ideally those interfaces aren't leaked to the user at all--the only person
who accesses them is the mapreduce framework itself, so they should remain an
implementation detail.
In which case, I think they shouldn't even be in JobContext. Amareshwari?
> Making distributed cache getters in JobContext never return null
> ----------------------------------------------------------------
>
> Key: MAPREDUCE-990
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-990
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Philip Zeyliger
> Assignee: Philip Zeyliger
> Priority: Minor
> Attachments: MAPREDUCE-990.patch.txt
>
>
> MAPREDUCE-898 moved distributed cache setters and getters into Job and
> JobContext. Since the API is new, I'd like to propose that those getters
> never return null, but instead always return an array, even if it's empty.
> If people don't like this change, I can instead merely update the javadoc to
> reflect the fact that null may be returned.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
