[
https://issues.apache.org/jira/browse/YARN-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889522#comment-15889522
]
Rohith Sharma K S edited comment on YARN-6199 at 3/1/17 5:39 AM:
-----------------------------------------------------------------
bq. Use-case wise, you plan to use this with daterange. Right?
Initially Yes, but it is not going to be scalable solution because data range
boundary is unlimited. Date Range do NOT solve all filter userid use case. Date
range retrieves all the users data. Lets say, userX has run a flow one week
back and userX wants to know about his flow activities. Can he able to
retrieves userX flows given data range? The response contains all the users
flow activities data.
bq. do you think this should be a merge blocker?
We can take consensus on this! It is important to support this filter. I do
not think of any easier solution to support this filter unless flow activity
table to be modified to keep userid in column. By doing this, at least column
filters can be used to match user id.
was (Author: rohithsharma):
bq. Use-case wise, you plan to use this with daterange. Right?
Date Range do NOT solve filter userid use case. Date range retrieves all the
users data. Lets say, userX has run a flow one week back and userX wants to
know about his flow activities. Can he able to retrieves userX flows given data
range? The response contains all the users flow activities data.
bq. do you think this should be a merge blocker?
We can take consensus on this! It is important to support this filter. I do
not think of any easier solution to support this filter unless flow activity
table to be modified to keep userid in column. By doing this, at least column
filters can be used to match user id.
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
