[
https://issues.apache.org/jira/browse/MAPREDUCE-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690534#comment-13690534
]
Stan Rosenberg commented on MAPREDUCE-5247:
-------------------------------------------
Kousuke,
HADOOP-7771 is a very interesting find! Based on my reading of the history,
the naming convention uses the suffix explicitly to make the corresponding
temporary (staging) file non-hidden. Indeed, the last comment in that jira is
a question by Daryn w.r.t. whether or not partially copied files should be
visible; there are no follow-ups to the question but the jira is closed. Since
the decision to have temporary files visible seems to be arbitrary, I propose
that we fix FsShell by making them hidden. Otherwise, this notion of partially
loaded files needs to be lifted to the level of FileInputFormat---jobs should
not be failing under normal conditions.
> FileInputFormat should filter files with '._COPYING_' sufix
> -----------------------------------------------------------
>
> Key: MAPREDUCE-5247
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5247
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Stan Rosenberg
>
> FsShell copy/put creates staging files with '._COPYING_' suffix. These files
> should be considered hidden by FileInputFormat. (A simple fix is to add the
> following conjunct to the existing hiddenFilter:
> {code}
> !name.endsWith("._COPYING_")
> {code}
> After upgrading to CDH 4.2.0 we encountered this bug. We have a legacy data
> loader which uses 'hadoop fs -put' to load data into hourly partitions. We
> also have intra-hourly jobs which are scheduled to execute several times per
> hour using the same hourly partition as input. Thus, as the new data is
> continuously loaded, these staging files (i.e., ._COPYING_) are breaking our
> jobs (since when copy/put completes staging files are moved).
> As a workaround, we've defined a custom input path filter and loaded it with
> "mapred.input.pathFilter.class".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
