[
https://issues.apache.org/jira/browse/HADOOP-13626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17236467#comment-17236467
]
Kihwal Lee commented on HADOOP-13626:
-------------------------------------
I believe this creates a compatibility issue. When the job submission env and
runtime env are different, distcp jobs cannot run due to this incompatibility.
Users who move in lock steps are fine, but we have a lot of diverse users and
interoperability is very critical. We had to revert it and a major change that
came after this to resolve the issue.
> Remove distcp dependency on FileStatus serialization
> ----------------------------------------------------
>
> Key: HADOOP-13626
> URL: https://issues.apache.org/jira/browse/HADOOP-13626
> Project: Hadoop Common
> Issue Type: Bug
> Components: tools/distcp
> Reporter: Christopher Douglas
> Assignee: Christopher Douglas
> Priority: Major
> Fix For: 2.9.0, 3.0.0-alpha2
>
> Attachments: HADOOP-13626.001.patch, HADOOP-13626.002.patch,
> HADOOP-13626.003.patch, HADOOP-13626.004.patch
>
>
> DistCp uses an internal struct {{CopyListingFileStatus}} to record metadata.
> Because this record extends {{FileStatus}}, it also relies on the
> {{Writable}} contract from that type. Because DistCp performs its checks on a
> subset of the fields (i.e., does not actually rely on {{FileStatus}} as a
> supertype), these types should be independent.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
