[
https://issues.apache.org/jira/browse/FALCON-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15146998#comment-15146998
]
Pallavi Rao commented on FALCON-1811:
-------------------------------------
After a conversation with [~pragya.mittal], although she is the seeing the
behavior we expect users to see. She is of the opinion that this is not
intuitive to users. When a user gives a start time, he expects to see instances
with that start time. So, here is my proposal:
When user supplies -start option, the default sortOrder can be ASC (start to
end). The user should be able to override this order by specifying -sortOrder
(DESC will show instances from end to start).
This change has to be applied not just to status API, but to all instance APIs
that take in start time and end time.
> Status API does not honour start option
> ---------------------------------------
>
> Key: FALCON-1811
> URL: https://issues.apache.org/jira/browse/FALCON-1811
> Project: Falcon
> Issue Type: Bug
> Components: client
> Affects Versions: trunk, 0.9
> Reporter: Pragya Mittal
> Assignee: Praveen Adlakha
>
> The result of status API is :
> {noformat}
> dataqa@lda01:~$ fipstatus processMerlinOozie -colo ua2 -numResults 2 -start
> 2016-02-02T12:59Z
> Consolidated Status: SUCCEEDED
> Instances:
> Instance Cluster SourceCluster Status
> Start End Details Log
> -----------------------------------------------------------------------------------------------
> 2016-02-02T13:08Z ProcessMultipleClustersTest-corp-3a97a54e -
> RUNNING 2016-02-02T13:08Z -
> -http://8RPCG32.corp.inmobi.com:11000/oozie?job=0001277-160202121302340-oozie-oozi-W
> actions:
> hdfscommands OK -
> aggregator SUCCEEDED
> http://8RPCG32.corp.inmobi.com:8088/proxy/application_1454048976510_7718/
> java-node SUCCEEDED
> http://8RPCG32.corp.inmobi.com:8088/proxy/application_1454048976510_7722/
> succeeded-post-processing RUNNING
> http://8RPCG32.corp.inmobi.com:8088/proxy/application_1454048976510_7726/
> 2016-02-02T13:07Z ProcessMultipleClustersTest-corp-3a97a54e -
> SUCCEEDED 2016-02-02T13:07Z 2016-02-02T13:07Z -
> http://8RPCG32.corp.inmobi.com:11000/oozie?job=0001274-160202121302340-oozie-oozi-W
> actions:
> hdfscommands OK -
> aggregator SUCCEEDED
> http://8RPCG32.corp.inmobi.com:8088/proxy/application_1454048976510_7709/
> java-node SUCCEEDED
> http://8RPCG32.corp.inmobi.com:8088/proxy/application_1454048976510_7713/
> Additional Information:
> Response: ua2/STATUS
> Request Id: ua2/1073468757@qtp-311239812-13 -
> 31efc585-41ae-48a3-9e53-515e71fe4243
> {noformat}
> Instead it should display two instances :
> 2016-02-02T12:59Z
> 2016-02-02T13:00Z
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
