You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Julia Kinga Marton (JIRA)" <ji...@apache.org> on 2018/02/21 13:35:00 UTC

[jira] [Assigned] (OOZIE-3177) Unclear ooziedb -sqlFile option behaviour

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

Julia Kinga Marton reassigned OOZIE-3177:
-----------------------------------------

    Assignee: Julia Kinga Marton

> Unclear ooziedb -sqlFile option behaviour 
> ------------------------------------------
>
>                 Key: OOZIE-3177
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3177
>             Project: Oozie
>          Issue Type: Bug
>          Components: scripts
>            Reporter: Julia Kinga Marton
>            Assignee: Julia Kinga Marton
>            Priority: Minor
>
> There are two scenarios when running ooziedb.sh with -sqlscript option can lead to misunderstandings:
> full command: ooziedb.sh upgrade -sqlfile oozie-upgrade.sql
>  # if there are no changes, the following information is printed out: "The SQL commands have been written to: oozie-upgrade.sql", however if there is no SQL command, the file will be not created. 
>  # If there are changes and the file is created, it is stored in the /tmp/ directory. In the log message it would be good to print out the full path to the file, not only the file name.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)