You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Robert Kanter (JIRA)" <ji...@apache.org> on 2015/03/31 20:23:52 UTC

[jira] [Updated] (OOZIE-2190) Fix conflicts between generated filenames and user filenames in actions

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

Robert Kanter updated OOZIE-2190:
---------------------------------
    Summary: Fix conflicts between generated filenames and user filenames in actions  (was: Fix filename conflicts in actions)

> Fix conflicts between generated filenames and user filenames in actions
> -----------------------------------------------------------------------
>
>                 Key: OOZIE-2190
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2190
>             Project: Oozie
>          Issue Type: Bug
>          Components: action
>            Reporter: Robert Kanter
>
> We've seen issues where if you have a hive-site.xml with the Hive action or a sqoop-site.xml with the Sqoop action, it fails because of a name conflict (the action wants to write a file with the same name).  We should go through all of the actions and look for any filenames that go into the working directory and try to fix these name conflicts.  Here are some ideas on how to fix this:
> # Generate a subdir in the working directory named "oozie-<timestamp>" and put all files generated by the action in there; it would be extremely unlikely for the user to have a directory named that.
> # Before creating any files in the action, we check if that file already exists and if so, rename it
> # Add "-<timestamp>" to the filenames generated by actions
> I think option 1 is the easiest and best for maintainability.  We can make some helper method that all of the actions can use that returns the directory that's created and just make sure to put any created files in there.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)