[
https://issues.apache.org/jira/browse/AMBARI-9462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14304273#comment-14304273
]
Hudson commented on AMBARI-9462:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #1680 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/1680/])
AMBARI-9462. Adding Hive Metastore changes core-site prop to final (sgunturi:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fcdbadd59be9fdb2defed94567560b33f4b43905)
* ambari-web/app/controllers/main/host/details.js
* ambari-web/test/controllers/main/host/details_test.js
> Adding Hive Metastore changes core-site prop to final
> -----------------------------------------------------
>
> Key: AMBARI-9462
> URL: https://issues.apache.org/jira/browse/AMBARI-9462
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Srimanth Gunturi
> Assignee: Srimanth Gunturi
> Fix For: 2.0.0
>
> Attachments: AMBARI-9462.patch, hive-lock.tiff
>
>
> 1) added hive metastore
> 2) hdfs core site is updated to handle proxyuser for hcat (to include both
> hosts, not just one), which is fine
> 3) but looks like fs.defaultFS is also switched from final to not final. This
> config prop change should not happen as part of adding a Hive Metastore
> component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
