ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrii Tkach (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-6068) Ambari web client should use stacks API instead of stacks2 API
Date Tue, 10 Jun 2014 16:03:03 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrii Tkach resolved AMBARI-6068.
----------------------------------

    Resolution: Fixed

> Ambari web client should use stacks API instead of stacks2 API
> --------------------------------------------------------------
>
>                 Key: AMBARI-6068
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6068
>             Project: Ambari
>          Issue Type: Task
>          Components: client
>    Affects Versions: 1.6.0
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>             Fix For: 1.6.1
>
>
> There are two hadoop stack endpoint
> {{http://localhost:8080/api/v1/stacks}}
> and
> {{http://localhost:8080/api/v1/stacks2}}
> Amabri web client uses stacks2 endpoint. Much of the work done in Ambari-1.6.0 for blueprint
support is  committed for stacks endpoint and it's not supported by stacks2 API. 
> Stacks2 API is deprecated
> Ambari web client should also use stacks endpoint for consistency



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message