Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5C607177DA for ; Wed, 5 Nov 2014 13:33:35 +0000 (UTC) Received: (qmail 48883 invoked by uid 500); 5 Nov 2014 13:33:35 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 48853 invoked by uid 500); 5 Nov 2014 13:33:35 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 48773 invoked by uid 99); 5 Nov 2014 13:33:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Nov 2014 13:33:35 +0000 Date: Wed, 5 Nov 2014 13:33:35 +0000 (UTC) From: "Hadoop QA (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-8156) Usability: Do not force a mysql restart to apply Hive changes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-8156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198366#comment-14198366 ] Hadoop QA commented on AMBARI-8156: ----------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12679522/AMBARI-8156.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {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:red}-1 core tests{color}. The patch failed these unit tests in ambari-server: org.apache.ambari.server.stageplanner.TestStagePlanner org.apache.ambari.server.orm.dao.AlertDefinitionDAOTest org.apache.ambari.server.state.alerts.AlertStateChangedEventTest org.apache.ambari.server.controller.AmbariManagementControllerImplTest org.apache.ambari.server.state.RequestExecutionTest org.apache.ambari.server.state.ConfigGroupTest org.apache.ambari.server.orm.entities.ViewInstanceEntityTest org.apache.ambari.server.actionmanager.TestActionManager org.apache.ambari.server.orm.DBAccessorImplTest org.apache.ambari.server.state.stack.OSFamilyTest org.apache.ambari.server.metadata.AgentAlertDefinitionsTest org.apache.ambari.server.actionmanager.ExecutionCommandWrapperTest org.apache.ambari.server.orm.dao.ServiceConfigDAOTest org.apache.ambari.server.api.services.AmbariMetaInfoTest org.apache.ambari.server.state.ServiceTest org.apache.ambari.server.state.cluster.AlertDataManagerTest org.apache.ambari.server.orm.TestOrmImpl org.apache.ambari.server.orm.dao.RequestDAOTest org.apache.ambari.server.api.services.PersistKeyValueImplTest org.apache.ambari.server.scheduler.ExecutionScheduleManagerTest org.apache.ambari.server.view.ViewRegistryTest org.apache.ambari.server.state.host.HostTest org.apache.ambari.server.state.alerts.AlertDefinitionHashTest org.apache.ambari.server.orm.JdbcPropertyTest org.apache.ambari.server.state.svccomphost.ServiceComponentHostTest org.apache.ambari.server.controller.AmbariCustomCommandExecutionHelperTest org.apache.ambari.server.api.services.PersistServiceTest org.apache.ambari.server.orm.dao.AlertsDAOTest org.apache.ambari.server.view.ViewSubResourceProviderTest org.apache.ambari.server.metadata.RoleCommandOrderTest org.apache.ambari.server.state.cluster.ClusterTest org.apache.ambari.server.state.ServiceComponentTest org.apache.ambari.server.notifications.EmailDispatcherTest org.apache.ambari.server.orm.dao.RequestScheduleDAOTest org.apache.ambari.server.orm.dao.HostConfigMappingDAOTest org.apache.ambari.server.view.ViewAmbariStreamProviderTest org.apache.ambari.server.metadata.RoleGraphTest org.apache.ambari.server.orm.dao.UpgradeDAOTest org.apache.ambari.server.actionmanager.TestActionDBAccessorImpl org.apache.ambari.server.orm.dao.ConfigGroupDAOTest org.apache.ambari.server.state.ConfigHelperTest org.apache.ambari.server.state.alerts.AlertEventPublisherTest org.apache.ambari.server.state.cluster.ClustersTest org.apache.ambari.server.view.ViewContextImplTest org.apache.ambari.server.events.EventsTest org.apache.ambari.server.orm.dao.AlertDispatchDAOTest Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/506//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/506//console This message is automatically generated. > Usability: Do not force a mysql restart to apply Hive changes > ------------------------------------------------------------- > > Key: AMBARI-8156 > URL: https://issues.apache.org/jira/browse/AMBARI-8156 > Project: Ambari > Issue Type: Improvement > Components: ambari-server > Affects Versions: 1.7.0 > Reporter: Szilard Nemethy > Assignee: Szilard Nemethy > Labels: ambari-server > Fix For: 2.0.0 > > Attachments: AMBARI-8156.patch > > > Ambari currently requires all services under tab to be restarted when changes are made to the configuration. This includes forcing a mysql restart when Hive settings are changed. Mysql should only have to be restarted when settings specific to mysql get changed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)