[jira] [Comment Edited] (OOZIE-2327) coord:latest(int n) does not give the information about the path

["Purshotam Shah (JIRA)" <ji...@apache.org>]

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

Purshotam Shah edited comment on OOZIE-2327 at 8/12/15 6:17 AM:
----------------------------------------------------------------

CoordActionInputCheckXCommand check hdfs papth every 90 sec and if we use "oozie.service.ELService.latest-el.use-current-time" and it's calculate path with relative to current time.
We need to do same behavior while checking path.
We are not going to show any random path.

{{coord:latest(int n)}}  is a very simple usecase and showing it as {{coord:latest(0)[\/data/metadata\/A\/\${YEAR}\/\${MONTH}\/\${DAY}\/\${HOUR}]}}  might help for some user.
But i am very sure that some user will still get confused as available data might be month old.

For usecase like {{coord:latest(-2000,0)}}, i don't think showing like {{coord:latest(-2000,0)[/data/metadata/A/\${YEAR}/\${MONTH}/\${DAY}/\${HOUR}]}} will help user anyway.
He wanted to know which dataset from -2000,0 is missing and I have seen lot of users struggling with that.

We need to compute path based on frequency, current time, start time etc.. and show them actual path, rather showing them uri-template and expecting them to compute path.  I guess user is expecting to see actual missing path rather than uri-template .



was (Author: puru):
CoordActionInputCheckXCommand check hdfs papth every 90 sec and if we use "oozie.service.ELService.latest-el.use-current-time" and it's calculate path with relative to current time.
We need to do same behavior while checking path.
We are not going to show any random path.

{{coord:latest(int n)}}  is a very simple usecase and showing it as {{coord:latest(0)[/data/metadata/A/\${YEAR}/\${MONTH}/\${DAY}/\${HOUR}]}}  might help for some user.
But i am very sure that some user will still get confused as available data might be month old.

For usecase like {{coord:latest(-2000,0)}}, i don't think showing like {{coord:latest(-2000,0)[/data/metadata/A/\${YEAR}/\${MONTH}/\${DAY}/\${HOUR}]}} will help user anyway.
He wanted to know which dataset from -2000,0 is missing and I have seen lot of users struggling with that.

We need to compute path based on frequency, current time, start time etc.. and show them actual path, rather showing them uri-template and expecting them to compute path.  I guess user is expecting to see actual missing path rather than uri-template .


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