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 06:43:09 UTC

[jira] [Created] (OOZIE-147) GH-125: Query GET_WORKFLOWS_COLUMNS should order by createdTimestamp

GH-125: Query GET_WORKFLOWS_COLUMNS should order by createdTimestamp
--------------------------------------------------------------------

                 Key: OOZIE-147
                 URL: https://issues.apache.org/jira/browse/OOZIE-147
             Project: Oozie
          Issue Type: Bug
            Reporter: Hadoop QA


A workflow job might be killed before start_time was given. To fix this, we have to
change the query of jobs to be sorted by created_time instead of start_time.

The query will be like this:
    select w.id, w.appName, w.status, w.run, w.user, w.group, w.createdTimestamp, 
    w.startTimestamp, w.lastModifiedTimestamp, w.endTimestamp from 
    WorkflowJobBean w order by w.createdTimestamp desc

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (OOZIE-147) GH-125: Query GET_WORKFLOWS_COLUMNS should order by createdTimestamp

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099835#comment-13099835 ] 

Hadoop QA commented on OOZIE-147:
---------------------------------

brookwc remarked:
Closed by 19e0f4bbafafa953f113c4cb9d3335ea608bcd8d Query GET_WORKFLOWS_COLUMNS should order by createdTimestamp instead of starttime

> GH-125: Query GET_WORKFLOWS_COLUMNS should order by createdTimestamp
> --------------------------------------------------------------------
>
>                 Key: OOZIE-147
>                 URL: https://issues.apache.org/jira/browse/OOZIE-147
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Hadoop QA
>
> A workflow job might be killed before start_time was given. To fix this, we have to
> change the query of jobs to be sorted by created_time instead of start_time.
> The query will be like this:
>     select w.id, w.appName, w.status, w.run, w.user, w.group, w.createdTimestamp, 
>     w.startTimestamp, w.lastModifiedTimestamp, w.endTimestamp from 
>     WorkflowJobBean w order by w.createdTimestamp desc

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Closed] (OOZIE-147) GH-125: Query GET_WORKFLOWS_COLUMNS should order by createdTimestamp

Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OOZIE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Shaposhnik closed OOZIE-147.
----------------------------------

    Resolution: Fixed

> GH-125: Query GET_WORKFLOWS_COLUMNS should order by createdTimestamp
> --------------------------------------------------------------------
>
>                 Key: OOZIE-147
>                 URL: https://issues.apache.org/jira/browse/OOZIE-147
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Hadoop QA
>
> A workflow job might be killed before start_time was given. To fix this, we have to
> change the query of jobs to be sorted by created_time instead of start_time.
> The query will be like this:
>     select w.id, w.appName, w.status, w.run, w.user, w.group, w.createdTimestamp, 
>     w.startTimestamp, w.lastModifiedTimestamp, w.endTimestamp from 
>     WorkflowJobBean w order by w.createdTimestamp desc

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira