Varun Saxena commented on YARN-4179:

The approach chosen in the patch is that date will be in format ddMMyyyy and 
timezone will be assumed as GMT.
Now the issue here is should we fix the format ? Across geographies the popular 
date format varies.

Another solution is that date range can be specified as seconds since epoch. 
Here the issue is that instead of a single date any timestamp can be specified 
within a day.
We can although normalize the timestamp in date range by converting it into top 
of the day timestamp and then firing the query to backend. 

So would welcome views from others on this regarding which approach to follow. 

> [reader implementation] support flow activity queries based on time
> -------------------------------------------------------------------
>                 Key: YARN-4179
>                 URL: https://issues.apache.org/jira/browse/YARN-4179
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-2928
>            Reporter: Sangjin Lee
>            Assignee: Varun Saxena
>            Priority: Minor
>         Attachments: YARN-4179-YARN-2928.01.patch
> This came up as part of YARN-4074 and YARN-4075.
> Currently the only query pattern that's supported on the flow activity table 
> is by cluster only. But it might be useful to support queries by cluster and 
> certain date or dates.

This message was sent by Atlassian JIRA

Reply via email to