You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Srimanth Gunturi (JIRA)" <ji...@apache.org> on 2015/02/03 20:46:35 UTC
[jira] [Commented] (AMBARI-9462) Adding Hive Metastore changes
core-site prop to final
[ https://issues.apache.org/jira/browse/AMBARI-9462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303850#comment-14303850 ]
Srimanth Gunturi commented on AMBARI-9462:
------------------------------------------
Tests pass
{noformat}
[exec]
[exec] 5311 tests complete (11 seconds)
[exec] 63 tests pending
[exec]
{noformat}
> 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)