S throw some IOExecptions or it will leave the file
> unexecuted till next job runs.
>
> -Original Message-
> From: Harsh J [mailto:ha...@cloudera.com]
> Sent: Tuesday, May 01, 2012 6:11 PM
> To: hdfs-user@hadoop.apache.org
> Subject: Re: File Integrity in HDFS
>
>
s or it will leave the file
> unexecuted till next job runs.
>
> -Original Message-
> From: Harsh J [mailto:ha...@cloudera.com]
> Sent: Tuesday, May 01, 2012 6:11 PM
> To: hdfs-user@hadoop.apache.org
> Subject: Re: File Integrity in HDFS
>
> Yes renames/moves
: Re: File Integrity in HDFS
Yes renames/moves are merely metadata changes, like on your local filesystem
(unless you move across partitions/disks, a concept that wouldn't apply to a
DFS).
On Tue, May 1, 2012 at 5:53 PM, Stuti Awasthi wrote:
> Thanks Harsh,
> I also looked that when w
t: Tuesday, May 01, 2012 5:22 PM
> To: hdfs-user@hadoop.apache.org
> Subject: Re: File Integrity in HDFS
>
> The easiest way out would be to rename files to pick-up-able name upon
> successful copy, or have the loading done to a different directory and
> rename/move the file w
: Harsh J [mailto:ha...@cloudera.com]
Sent: Tuesday, May 01, 2012 5:22 PM
To: hdfs-user@hadoop.apache.org
Subject: Re: File Integrity in HDFS
The easiest way out would be to rename files to pick-up-able name upon
successful copy, or have the loading done to a different directory and
rename/move the
The easiest way out would be to rename files to pick-up-able name upon
successful copy, or have the loading done to a different directory and
rename/move the file when successfully closed to the job input
directory.
On Tue, May 1, 2012 at 3:22 PM, Stuti Awasthi wrote:
> Hi All,
>
>
>
> I have a s
