falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pallavi Rao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1811) Status API does not honour start option
Date Fri, 12 Feb 2016 09:51:18 GMT

    [ https://issues.apache.org/jira/browse/FALCON-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144329#comment-15144329
] 

Pallavi Rao commented on FALCON-1811:
-------------------------------------

[~pragya.mittal], here is the behavior you are noticing. Lets say there are 20 instances till
"now", for a given entity, i0 - i20. You specify startTime as i11 in your query and no numResults.
In this case, endTime defaults to "now" and instances i11 - i20 are retrieved and are ordered
in descending order of instance time (by default). So, you'll see i20 - i11 in the output.


Now, lets add numResults = 2 to the query. What this does is truncates result set to top 2.
Equivalent to "head -n". So, you will see i20 and i19. So, the query is honoring the start
option, but, due to truncation you don't see the the instances with the start you have specified.

> 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)

Mime
View raw message