[
https://issues.apache.org/jira/browse/KNOX-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717323#comment-16717323
]
Sandeep More commented on KNOX-1031:
------------------------------------
[~sunilg] I am assuming you are talking about the <trackingUrl> part. It might
not be supported by Knox as of now, but it could be supported by downstream
applications, given this is an API, the consumer of this API would probably
expect this URL to be consumable. It also does not look right not to rewrite
this one url. It should be relatively easy to rewrite using a html or xml
filter to rewrite it with \{$serviceUrl[AMBARIUI]} path, my thoughts.
> Apache Hadoop Timeline Server REST API support
> ----------------------------------------------
>
> Key: KNOX-1031
> URL: https://issues.apache.org/jira/browse/KNOX-1031
> Project: Apache Knox
> Issue Type: New Feature
> Components: Server
> Affects Versions: 0.13.0
> Environment: Apache Hadoop clusters, HortonWorks clusters, Cloudera
> clusters, MapR clusters
> Reporter: Pierre Beauvois
> Assignee: Sunil Govindan
> Priority: Major
> Fix For: 1.3.0
>
> Attachments: KNOX-1031.001.patch, KNOX-1031.002.patch
>
>
> Timeline Server REST API as documented here: [Timeline Server REST
> API|https://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/TimelineServer.html#Timeline_Server_REST_API_v1]
> The TLS REST API provides a RESTful interface to a Timeline Server. It makes
> it easy to produce and consume messages, view the state of the cluster, and
> perform administrative actions
> This feature allow to call Timeline Server REST API through Knox. It could be
> enabled in your topology by adding the following sample:
> {code:java}
> <service>
> <role>TIMELINESERVER</role>
> <url>http://{timelineserver-host}:{timelineserver-port}</url>
> </service>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
