[
https://issues.apache.org/jira/browse/OOZIE-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14692913#comment-14692913
]
Jaydeep Vishwakarma commented on OOZIE-2327:
--------------------------------------------
Some issue with formatting, Sending message again.
[~puru] Showing some random path would not make any sense. We cannot assume
some path and show it to the user , As {noformat} ${coord:latest(int n)}
{noformat} is not relative to the coordinator action creation (materialization)
time, it is the nth latest instance available when the action is started (when
the workflow job is started).
One of the reason of input path unavailability could be the missing of
done-flag in latest path and that latest path belongs to some very old time
compare to current time and in this case showing some recent path will
completely miss lead to the user.
Currently we show missing input for latest path like !!${coord:latest(0) ,
instead of this we can show something like {noformat}
coord:latest(0)[/data/metadata/A/${YEAR}/${MONTH}/${DAY}/${HOUR}] {noformat} .
I think It will not miss lead to the user.
> coord:latest(int n) does not give the information about the path
> ----------------------------------------------------------------
>
> Key: OOZIE-2327
> URL: https://issues.apache.org/jira/browse/OOZIE-2327
> Project: Oozie
> Issue Type: Bug
> Reporter: Jaydeep Vishwakarma
> Assignee: Jaydeep Vishwakarma
>
> User used to face difficulty when coord instance wait for coord:latest( n ).
> As oozie -info does not show which path it is waiting for. At the user end
> has to see the coord definition. If we show uri-template it will improve
> debuggability.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
