You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Alejandro Abdelnur (Updated) (JIRA)" <ji...@apache.org> on 2012/03/02 23:38:38 UTC

[jira] [Updated] (OOZIE-300) GH-461: Mapping the workflow ID to coordinator ID

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

Alejandro Abdelnur updated OOZIE-300:
-------------------------------------

    Fix Version/s: pre-Apache
    
> GH-461: Mapping the workflow ID to coordinator ID
> -------------------------------------------------
>
>                 Key: OOZIE-300
>                 URL: https://issues.apache.org/jira/browse/OOZIE-300
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Hadoop QA
>             Fix For: pre-Apache
>
>
> Currently, Oozie doesn't seem to expose any programmatic way of identifying the coordinator ID (in particular which
> action ID) that actually spawned a given workflow. Can you please check if this already exists & let us know? If
> not, we would need this feature at the earliest as it's becoming really a pain to run a wild query on all coordinator
> applications & grep this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira