[
https://issues.apache.org/jira/browse/AMBARI-13261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939391#comment-14939391
]
Hudson commented on AMBARI-13261:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #3575 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3575/])
AMBARI-13261: Modify repository version resource handler update RESTful
(jluniya:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c538a4d2c900b90aeae92181a93a10bc5ede75c6])
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProviderTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProvider.java
> Modify repository version resource handler update RESTful API to update
> metaInfo table as well
> ----------------------------------------------------------------------------------------------
>
> Key: AMBARI-13261
> URL: https://issues.apache.org/jira/browse/AMBARI-13261
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.0
> Reporter: Nahappan Somasundaram
> Assignee: Nahappan Somasundaram
> Fix For: 2.2.0
>
>
> As we transition from metaInfo table to repo_version table, updating
> repo_version table must update metaInfo table so that scenarios that read
> from metaInfo table get the correct URLs. This will also help with fixing
> BUG-40202 - Disable old APIs to manage baseurl values.
> During cluster setup, the UI uses the old API to write to metaInfo table.
> During services installation, this information gets replicated to
> repo_version table. The UI will be modified to use the new API (repo_version
> table API) to store the URLs. However, for backward compatibility, we need
> this information in metaInfo table as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
