Andras Salamon created OOZIE-3519:
-------------------------------------
Summary: Invalid order of action listing for workflow
Key: OOZIE-3519
URL: https://issues.apache.org/jira/browse/OOZIE-3519
Project: Oozie
Issue Type: Bug
Affects Versions: trunk
Reporter: Andras Salamon
When I run the [demo
workflow|https://github.com/apache/oozie/blob/master/examples/src/main/apps/demo/workflow.xml]
using Oracle database and later read the information of the worklow the result
looks correct:
{noformat}
$ oozie job -info 0000000-190624053613443-oozie-oozi-W
Job ID : 0000000-190624053613443-oozie-oozi-W
------------------------------------------------------------------------------------------------------------------------------------
Workflow Name : demo-wf
...
Actions
------------------------------------------------------------------------------------------------------------------------------------
ID
Status Ext ID Ext Status Err Code
------------------------------------------------------------------------------------------------------------------------------------
0000000-190624053613443-oozie-oozi-W@:start:
OK - OK -
------------------------------------------------------------------------------------------------------------------------------------
0000000-190624053613443-oozie-oozi-W@cleanup-node
OK - OK -
------------------------------------------------------------------------------------------------------------------------------------
0000000-190624053613443-oozie-oozi-W@fork-node
OK - OK -
------------------------------------------------------------------------------------------------------------------------------------
0000000-190624053613443-oozie-oozi-W@pig-node
OK application_1561379784143_0002SUCCEEDED -
------------------------------------------------------------------------------------------------------------------------------------
0000000-190624053613443-oozie-oozi-W@streaming-node
OK application_1561379784143_0001SUCCEEDED -
------------------------------------------------------------------------------------------------------------------------------------
0000000-190624053613443-oozie-oozi-W@join-node
OK - OK -
------------------------------------------------------------------------------------------------------------------------------------
0000000-190624053613443-oozie-oozi-W@mr-node
OK application_1561379784143_0005SUCCEEDED -
------------------------------------------------------------------------------------------------------------------------------------
0000000-190624053613443-oozie-oozi-W@decision-node
OK - hdfs-node -
------------------------------------------------------------------------------------------------------------------------------------
0000000-190624053613443-oozie-oozi-W@hdfs-node
OK - OK -
------------------------------------------------------------------------------------------------------------------------------------
0000000-190624053613443-oozie-oozi-W@end
OK - OK -
------------------------------------------------------------------------------------------------------------------------------------
{noformat}
On the other hand, when I use mariadb, the result is the following:
{noformat}
$ oozie job -info 0000009-190617011505203-oozie-oozi-W
Job ID : 0000009-190617011505203-oozie-oozi-W
------------------------------------------------------------------------------------------------------------------------------------
Workflow Name : demo-wf
...
Actions
------------------------------------------------------------------------------------------------------------------------------------
ID Status Ext ID Ext Status Err Code
------------------------------------------------------------------------------------------------------------------------------------
0000009-190617011505203-oozie-oozi-W@:start: OK - OK -
------------------------------------------------------------------------------------------------------------------------------------
0000009-190617011505203-oozie-oozi-W@pig-node OK - OK -
------------------------------------------------------------------------------------------------------------------------------------
0000009-190617011505203-oozie-oozi-W@fork-node OK - OK -
------------------------------------------------------------------------------------------------------------------------------------
0000009-190617011505203-oozie-oozi-W@cleanup-node OK - OK -
------------------------------------------------------------------------------------------------------------------------------------
0000009-190617011505203-oozie-oozi-W@streaming-node OK
application_1560759315236_0041SUCCEEDED -
------------------------------------------------------------------------------------------------------------------------------------
0000009-190617011505203-oozie-oozi-W@mr-node OK
application_1560759315236_0043SUCCEEDED -
------------------------------------------------------------------------------------------------------------------------------------
0000009-190617011505203-oozie-oozi-W@join-node OK - OK -
------------------------------------------------------------------------------------------------------------------------------------
0000009-190617011505203-oozie-oozi-W@end OK - OK -
------------------------------------------------------------------------------------------------------------------------------------
0000009-190617011505203-oozie-oozi-W@hdfs-node OK - OK -
------------------------------------------------------------------------------------------------------------------------------------
0000009-190617011505203-oozie-oozi-W@decision-node OK - hdfs-node -
------------------------------------------------------------------------------------------------------------------------------------
{noformat}
In the latter case the order of the actions are not correct. I think we
[order|https://github.com/apache/oozie/blob/master/core/src/main/java/org/apache/oozie/WorkflowActionBean.java#L140-L141]
the list by the start timestamp, which might give incorrect orders if the
database only stored seconds and not milliseconds.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
