[
https://issues.apache.org/jira/browse/OOZIE-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069859#comment-14069859
]
Shwetha G S commented on OOZIE-1930:
------------------------------------
What I asked in OOZIE-1532 is the behaviour when both start and len are
specified. You fixed it correctly and works as expected. Thank you
Now the discussion is about what should the behaviour be when start is not
specified, but only len is specified. I think this should be the expected
output for various scenario:
Assuming coord has actions from C@11 to C@20 in DB(10 actions are purged)
{noformat}
oozie job -info <id> -start 12 -len 5 [-order desc] --> returns C@16 to C@12
oozie job -info <id> -start 12 -len 5 -order asc --> returns C@12 to C@16
oozie job -info <id> -len 5 [-order desc] --> returns C@20 to C16
oozie job -info <id> -len 5 -order asc --> returns C@11 to C15
{noformat}
In code, we can achieve this behaviour by not adding id clause in the query
when start is not specified in the API. Does this make sense?
> oozie coordinator "-info desc" returns earliest instead of latest actions
> when specifying "len" after oozie-1532
> ----------------------------------------------------------------------------------------------------------------
>
> Key: OOZIE-1930
> URL: https://issues.apache.org/jira/browse/OOZIE-1930
> Project: Oozie
> Issue Type: Bug
> Reporter: Bowen Zhang
> Assignee: Bowen Zhang
> Fix For: 4.1.0
>
> Attachments: oozie-1930.patch, oozie-1930.patch
>
>
> This one definitely needs to be part of 4.1
--
This message was sent by Atlassian JIRA
(v6.2#6252)
