[
https://issues.apache.org/jira/browse/OOZIE-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073815#comment-14073815
]
Purshotam Shah commented on OOZIE-1930:
---------------------------------------
{quote}
After looking at the old behavior and particularly the usage of "offset", I
tend to agree with Purshotam Shah, "offset" is not action number and it's
probably a mistake for us to change the behavior in oozie-1532. "offset" is
applied to the resulting set of mysql query. A command of "oozie job -info <id>
-offset 12 -len 5 -order desc" should return C5-C9 since the result set of "len
-5 -order desc" is C20-C1 and we start at the 12th record which is C9.
Generally speaking, suppose there is a table of "Student" ids from 1-100.
"select id from student order by id desc limit 20 offset 10" will return ids
70-90. "Select id from student where id > 40 order by id asc limit 20 offset
10" returns ids 51-70.
"-offset X -len Y -order desc -filter W=Z" should translate into "select * from
coord_actions where W=Z order by id desc limit Y offset X-1". The translation
is as simple as that which is the old behavior prior to oozie-1532.
Offset being the action number makes little sense when using descending order
with some filter applying.
Purshotam Shah, agree with this analysis?
{quote}
Agree.
> 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)
