You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Satish Subhashrao Saley (JIRA)" <ji...@apache.org> on 2016/07/26 20:27:20 UTC
[jira] [Updated] (OOZIE-2623) Oozie should use a dummy OutputFormat
[ https://issues.apache.org/jira/browse/OOZIE-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Satish Subhashrao Saley updated OOZIE-2623:
-------------------------------------------
Attachment: OOZIE-2623-1.patch
> Oozie should use a dummy OutputFormat
> -------------------------------------
>
> Key: OOZIE-2623
> URL: https://issues.apache.org/jira/browse/OOZIE-2623
> Project: Oozie
> Issue Type: Bug
> Reporter: Satish Subhashrao Saley
> Attachments: OOZIE-2623-1.patch
>
>
> After fixing OOZIE-2475, killed actions have this exception.
> {code}
> 2016-06-13 20:49:46,068 [uber-SubtaskRunner] WARN org.apache.hadoop.mapred.LocalContainerLauncher - Exception running local (uberized) 'child' : org.apache.hadoop.ipc.RemoteException(java.io.FileNotFoundException): Invalid inode path: /user/rohinip/oozie_LL/0266574-160613173929807-oozie_LL-W/pig1--pig/output/_temporary/1/_temporary/attempt_1464982500298_46637_m_000000_0/part-00000 (id=316134636)
> {code}
> This is because it currently uses FileOuputFormat and sets output directory to <actiondir>/output which is unnecessary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)