You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2011/09/08 07:13:09 UTC
[jira] [Created] (OOZIE-300) GH-461: Mapping the workflow ID to
coordinator ID
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
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (OOZIE-300) GH-461: Mapping the workflow ID to
coordinator ID
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik closed OOZIE-300.
----------------------------------
Resolution: Fixed
> 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OOZIE-300) GH-461: Mapping the workflow ID to
coordinator ID
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099972#comment-13099972 ]
Hadoop QA commented on OOZIE-300:
---------------------------------
brookwc remarked:
Closed by 41b6ad1327699141fb6f67cd63adcbceba9b3a9c Mapping the workflow ID to coordinator ID
> 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira