Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 6 Jun 2017 18:24:18 +0000 (UTC)
From: "Varun Saxena (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13043256.1487164229000.9061.1496773458482@Atlassian.JIRA>
In-Reply-To: <JIRA.13043256.1487164229000@Atlassian.JIRA>
References: <JIRA.13043256.1487164229000@Atlassian.JIRA> <JIRA.13043256.1487164229070@jira-lw-us.apache.org>
Subject: [jira] [Commented] (YARN-6199) Support for listing flows with
 filter userid
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 06 Jun 2017 18:24:28 -0000


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

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

bq. A known issue is that since it is using a regex string comparator, it gives results even when the specified user id is only a substring of what's in the table. Any suggestion to address this?
We currently use Separator#QUALIFIERS (or ! character) to separate different segments in a rowkey. We can probably put ! characters before and after userid to ensure full match happens.

Also should we use SubstringComparator instead of RegexStringComparator? Regex matches might be slower. I found this issue HBASE-9428 which says Regex filters are at least an order of magnitude slower since 0.94.3. I am not sure if it is as good as substring matching in the version we are using or not. 
Either ways SubstringComparator should serve our use case.

However to avoid full table scan we should use userid with suitable daterange filter. This can be left as a note in the documentation in the documentation JIRA.


> 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
>            Assignee: Haibo Chen
>         Attachments: YARN-6199.00.patch
>
>
> 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