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 "Steve Loughran (Jira)" <ji...@apache.org> on 2022/06/22 12:25:00 UTC

[jira] [Updated] (MAPREDUCE-7371) DistributedCache alternative APIs should not use DistributedCache APIs internally

     [ https://issues.apache.org/jira/browse/MAPREDUCE-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran updated MAPREDUCE-7371:
--------------------------------------
    Fix Version/s: 3.3.9

> DistributedCache alternative APIs should not use DistributedCache APIs internally
> ---------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-7371
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7371
>             Project: Hadoop Map/Reduce
>          Issue Type: Task
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0, 3.3.9
>
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> DistributedCache has been deprecated long back and it's still being used as of today. However, all the alternative Job APIs (for deprecated DistributedCache APIs) still internally use DistributedCache APIs only, this is a deadlock and it leaves no room for removal of DistributedCache APIs in future. We should move core logic to Job or JobContext as required and let deprecated DistributedCache APIs point to the right alternatives internally.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org