[
https://issues.apache.org/jira/browse/YARN-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934848#comment-14934848
]
Varun Saxena commented on YARN-4075:
------------------------------------
[~gtCarrera9],
bq. A quick question: if I would like to query for a flow run with flow name
flow_1437599248581_1 and flow run id 1, shall I call the rest api as:
http://localhost:8188/ws/v2/timeline/flowrun/yarn_cluster/flow_1437599248581_1/1
You need to specify user as an optional query param if user in the request is
not same as the record you are seeking. I think that is what is happening for
you. User is part of row key in flow run table.
Query should be something like
http://localhost:8188/ws/v2/timeline/flowrun/yarn_cluster/flow_1437599248581_1/1?userid=some_user
NPE is because HBase reader is reading the result even though row key does not
match.
Should have added a UT case for row not matching. All of us missed it.
Will file a separate JIRA for this bug.
> [reader REST API] implement support for querying for flows and flow runs
> ------------------------------------------------------------------------
>
> Key: YARN-4075
> URL: https://issues.apache.org/jira/browse/YARN-4075
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Affects Versions: YARN-2928
> Reporter: Sangjin Lee
> Assignee: Varun Saxena
> Attachments: YARN-4075-YARN-2928.03.patch,
> YARN-4075-YARN-2928.04.patch, YARN-4075-YARN-2928.05.patch,
> YARN-4075-YARN-2928.POC.1.patch, YARN-4075-YARN-2928.POC.2.patch
>
>
> We need to be able to query for flows and flow runs via REST.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
