You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2017/03/09 18:23:38 UTC

[jira] [Commented] (AMBARI-20370) Fix up tez view version

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

Hadoop QA commented on AMBARI-20370:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12856968/AMBARI-20370_branch-2.5.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/10951//console

This message is automatically generated.

> Fix up tez view version
> -----------------------
>
>                 Key: AMBARI-20370
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20370
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-views
>    Affects Versions: 2.5.0
>            Reporter: Nitiraj Singh Rathore
>            Assignee: Nitiraj Singh Rathore
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-20370_branch-2.5.patch
>
>
> Currently tez view version uses version and build in url. Because of this everytime tez view is changed the value of tez.tez-ui.history-url.base needs to be changed in tez-site.
> This url should no be fixed to auto tez view instance's short url.



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