hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Saxena (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6199) Support for listing flows with filter userid
Date Wed, 01 Mar 2017 20:05:45 GMT

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

Varun Saxena commented on YARN-6199:
------------------------------------

bq. The response contains all the users flow activities data.
What I actually meant was that when you use userid filter for what I presume is a Web UI use
case, will you be using it with daterange filter? Because otherwise we will have a full table
scan. daterange would limit the scan to some degree depending on the range specified.
I was not suggesting using existing daterange filter to retrieve user specific records.
As you said userX may have run a flow, a week ago. I hope the use case is not something on
the lines of retrieve last 10 flows, say, executed by userX. Because some user may have run
flows even a year ago. And we cannot be doing a humongous scan for even the default view for
that user in UI.

I hope UI can be designed in a manner wherein you can show data based on a predetermined date
range(say, current day, last 3 days, etc.).
Also an option can be provided to specify a date which can be selected to query records for
other date ranges....

We can add a user column in flow activity table to restrict rows retrieved from backend.

Whether its a merge blocker or not, depends entirely on how important it is for you. :)

> Support for listing flows with filter userid
> --------------------------------------------
>
>                 Key: YARN-6199
>                 URL: https://issues.apache.org/jira/browse/YARN-6199
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelinereader
>            Reporter: Rohith Sharma K S
>              Labels: yarn-5355-merge-blocker
>
> Currently */flows* API retrieves flow entities for all the users by default. It is required
to provide filter user i.e */flows?user=rohith* . This is critical filter in secured environment.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message