[
https://issues.apache.org/jira/browse/AMBARI-14212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041727#comment-15041727
]
Hadoop QA commented on AMBARI-14212:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12775777/AMBARI-14212_branch-2.1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 7 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server ambari-views contrib/views/hive contrib/views/pig
contrib/views/utils.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/4488//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4488//console
This message is automatically generated.
> Changes in Instance Definition does not get reflects in pig and hive view due
> to caching in UserLocal.java
> ----------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-14212
> URL: https://issues.apache.org/jira/browse/AMBARI-14212
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
> Affects Versions: 2.1.2
> Reporter: Gaurav Nagar
> Assignee: Gaurav Nagar
> Priority: Critical
> Fix For: 2.2.0
>
> Attachments: AMBARI-14212_branch-2.1.patch,
> AMBARI-14212_branch-2.1_02.patch
>
>
> Connections in different views are cached in the ViewContext, through the
> UserLocal objects of the respective views. However, on update of
> configuration parameters of the view instance, the connection for the
> instance in the UserLocal object is not refreshed. This causes a failure in
> connection to the new/updated data node. The solution to this is the drop the
> instance specific connection and on new request from the browser ,
> re-establish the connection with the data node, and update the UserLocal
> objects.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
