[jira] [Commented] (AMBARI-12772) Adding host via blueprint fails on secure cluster

[ https://issues.apache.org/jira/browse/AMBARI-12772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726781#comment-14726781 ] Hadoop QA commented on AMBARI-12772: {color:green}+1 overall{color}. Here are the r

Re: Possible Ambari 2.1 rollingupgrade/downgrade defect when using configuration groups?

Hello Alejandro, Yes, I have created JIRA AMBARI-12949 for the issue. https://issues.apache.org/jira/browse/AMBARI-12949 Thank you. Di Li InfoSphere BigInsights IBM Ottawa Lab Palladium Campus Email: d...@ca.ibm.com Phone: 613-270-4883, Tie-line:315-4883 From: Alejandro Fernandez To:

[jira] [Commented] (AMBARI-12969) sys_prepped clusters should not have to copy tarballs again

[ https://issues.apache.org/jira/browse/AMBARI-12969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726731#comment-14726731 ] Sumit Mohanty commented on AMBARI-12969: Tested on a host that is sys_prepped an

[jira] [Updated] (AMBARI-12969) sys_prepped clusters should not have to copy tarballs again

[ https://issues.apache.org/jira/browse/AMBARI-12969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-12969: --- Attachment: AMBARI-12969.patch > sys_prepped clusters should not have to copy tarballs again

[jira] [Created] (AMBARI-12969) sys_prepped clusters should not have to copy tarballs again

Sumit Mohanty created AMBARI-12969: -- Summary: sys_prepped clusters should not have to copy tarballs again Key: AMBARI-12969 URL: https://issues.apache.org/jira/browse/AMBARI-12969 Project: Ambari

[jira] [Commented] (AMBARI-12968) Hosts page 'clear filters' link does not work

[ https://issues.apache.org/jira/browse/AMBARI-12968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726699#comment-14726699 ] Hadoop QA commented on AMBARI-12968: {color:green}+1 overall{color}. Here are the r

Re: Review Request 37984: Stop-and-Start Upgrade: DB Schema Changes

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37984/ --- (Updated Sept. 2, 2015, 3:54 a.m.) Review request for Ambari, Dmytro Grinenko,

[jira] [Updated] (AMBARI-12699) Stop-and-Start Upgrade: DB Schema Changes

[ https://issues.apache.org/jira/browse/AMBARI-12699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-12699: - Attachment: (was: AMBARI-12699.patch) > Stop-and-Start Upgrade: DB Schema Ch

[jira] [Updated] (AMBARI-12699) Stop-and-Start Upgrade: DB Schema Changes

[ https://issues.apache.org/jira/browse/AMBARI-12699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-12699: - Attachment: AMBARI-12699.patch > Stop-and-Start Upgrade: DB Schema Changes > ---

[jira] [Commented] (AMBARI-12965) Selection of SQLA should warn user that it is supported only for HDP-2.3.2 and beyond

[ https://issues.apache.org/jira/browse/AMBARI-12965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726669#comment-14726669 ] Hudson commented on AMBARI-12965: - FAILURE: Integrated in Ambari-trunk-Commit #3368 (See

[jira] [Commented] (AMBARI-12965) Selection of SQLA should warn user that it is supported only for HDP-2.3.2 and beyond

[ https://issues.apache.org/jira/browse/AMBARI-12965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726656#comment-14726656 ] Hudson commented on AMBARI-12965: - SUCCESS: Integrated in Ambari-branch-2.1 #461 (See [

[jira] [Commented] (AMBARI-12951) Prompt user to save checkpoint before shutdown if last checkpoint is too old

[ https://issues.apache.org/jira/browse/AMBARI-12951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726570#comment-14726570 ] Hudson commented on AMBARI-12951: - SUCCESS: Integrated in Ambari-trunk-Commit #3367 (See

[jira] [Commented] (AMBARI-12476) Widget response differs when using ambarisessionid and basic auth

[ https://issues.apache.org/jira/browse/AMBARI-12476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726571#comment-14726571 ] Hudson commented on AMBARI-12476: - SUCCESS: Integrated in Ambari-trunk-Commit #3367 (See

[jira] [Commented] (AMBARI-12951) Prompt user to save checkpoint before shutdown if last checkpoint is too old

[ https://issues.apache.org/jira/browse/AMBARI-12951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726552#comment-14726552 ] Hudson commented on AMBARI-12951: - FAILURE: Integrated in Ambari-branch-2.1 #460 (See [

[jira] [Commented] (AMBARI-12476) Widget response differs when using ambarisessionid and basic auth

[ https://issues.apache.org/jira/browse/AMBARI-12476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726553#comment-14726553 ] Hudson commented on AMBARI-12476: - FAILURE: Integrated in Ambari-branch-2.1 #460 (See [

[jira] [Commented] (AMBARI-12965) Selection of SQLA should warn user that it is supported only for HDP-2.3.2 and beyond

[ https://issues.apache.org/jira/browse/AMBARI-12965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726496#comment-14726496 ] Hadoop QA commented on AMBARI-12965: {color:red}-1 overall{color}. Here are the res

[jira] [Updated] (AMBARI-12968) Hosts page 'clear filters' link does not work

[ https://issues.apache.org/jira/browse/AMBARI-12968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-12968: -- Attachment: AMBARI-12968.patch > Hosts page 'clear filters' link does not work > -

Review Request 38035: Hosts page 'clear filters' link does not work

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/38035/ --- Review request for Ambari, Jaimin Jetly and Yusaku Sako. Bugs: AMBARI-12968

Re: Review Request 37690: Adding host via blueprint fails on secure cluster

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37690/ --- (Updated Sept. 1, 2015, 8:27 p.m.) Review request for Ambari, Jonathan Hurley,

[jira] [Updated] (AMBARI-12772) Adding host via blueprint fails on secure cluster

[ https://issues.apache.org/jira/browse/AMBARI-12772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-12772: -- Attachment: AMBARI-12772_trunk_02.patch > Adding host via blueprint fails on secure cluster >

[jira] [Commented] (AMBARI-12965) Selection of SQLA should warn user that it is supported only for HDP-2.3.2 and beyond

[ https://issues.apache.org/jira/browse/AMBARI-12965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726466#comment-14726466 ] Yusaku Sako commented on AMBARI-12965: -- +1 for the patch. > Selection of SQLA shou

[jira] [Updated] (AMBARI-12965) Selection of SQLA should warn user that it is supported only for HDP-2.3.2 and beyond

[ https://issues.apache.org/jira/browse/AMBARI-12965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-12965: Attachment: AMBARI-12965_2.patch > Selection of SQLA should warn user that it is supported

[jira] [Resolved] (AMBARI-12476) Widget response differs when using ambarisessionid and basic auth

[ https://issues.apache.org/jira/browse/AMBARI-12476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle resolved AMBARI-12476. -- Resolution: Fixed > Widget response differs when using ambarisessionid and basic auth

[jira] [Commented] (AMBARI-12476) Widget response differs when using ambarisessionid and basic auth

[ https://issues.apache.org/jira/browse/AMBARI-12476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726457#comment-14726457 ] Siddharth Wagle commented on AMBARI-12476: -- Pushed patch to branch-2.1 and diff

[jira] [Updated] (AMBARI-12476) Widget response differs when using ambarisessionid and basic auth

[ https://issues.apache.org/jira/browse/AMBARI-12476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-12476: - Fix Version/s: 2.1.2 > Widget response differs when using ambarisessionid and basic auth

[jira] [Updated] (AMBARI-12476) Widget response differs when using ambarisessionid and basic auth

[ https://issues.apache.org/jira/browse/AMBARI-12476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-12476: - Attachment: AMBARI-12476.trunk.patch > Widget response differs when using ambarisessioni

[jira] [Updated] (AMBARI-12965) Selection of SQLA should warn user that it is supported only for HDP-2.3.2 and beyond

[ https://issues.apache.org/jira/browse/AMBARI-12965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-12965: Attachment: AMBARI-12965.patch > Selection of SQLA should warn user that it is supported o

[jira] [Updated] (AMBARI-12965) Selection of SQLA should warn user that it is supported only for HDP-2.3.2 and beyond

[ https://issues.apache.org/jira/browse/AMBARI-12965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-12965: Attachment: (was: AMBARI-12965.patch) > Selection of SQLA should warn user that it is

[jira] [Commented] (AMBARI-12476) Widget response differs when using ambarisessionid and basic auth

[ https://issues.apache.org/jira/browse/AMBARI-12476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726432#comment-14726432 ] Sumit Mohanty commented on AMBARI-12476: +1 to backport the change > Widget res

[jira] [Updated] (AMBARI-12476) Widget response differs when using ambarisessionid and basic auth

[ https://issues.apache.org/jira/browse/AMBARI-12476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-12476: - Attachment: AMBARI-12476-2.1.2.patch Current patch + WidgetLayoutService fix. > Widget

[jira] [Created] (AMBARI-12968) Hosts page 'clear filters' link does not work

Richard Zang created AMBARI-12968: - Summary: Hosts page 'clear filters' link does not work Key: AMBARI-12968 URL: https://issues.apache.org/jira/browse/AMBARI-12968 Project: Ambari Issue Type

[jira] [Reopened] (AMBARI-12476) Widget response differs when using ambarisessionid and basic auth

[ https://issues.apache.org/jira/browse/AMBARI-12476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle reopened AMBARI-12476: -- Issue still present with WidgetLayoutService. > Widget response differs when using ambari

Re: Review Request 37979: Prompt user to save checkpoint before shutdown if last checkpoint is too old

> On Sept. 1, 2015, 3:49 p.m., Yusaku Sako wrote: > > This looks good. We can commit this, but let's have two follow-up actions. > > * Create a JIRA to add unit tests for all different scenarios mentioned. > > * Create a JIRA for making the HDFS username portion of the checkpoint > > command de

[jira] [Created] (AMBARI-12967) Make HDFS username portion of the checkpoint command description dynamic

Xi Wang created AMBARI-12967: Summary: Make HDFS username portion of the checkpoint command description dynamic Key: AMBARI-12967 URL: https://issues.apache.org/jira/browse/AMBARI-12967 Project: Ambari

[jira] [Created] (AMBARI-12966) Create Unit Tests for "Prompt user to save checkpoint before shutdown HDFS if last checkpoint is too old"

Xi Wang created AMBARI-12966: Summary: Create Unit Tests for "Prompt user to save checkpoint before shutdown HDFS if last checkpoint is too old" Key: AMBARI-12966 URL: https://issues.apache.org/jira/browse/AMBARI-1296

Re: Review Request 37979: Prompt user to save checkpoint before shutdown if last checkpoint is too old

> On Sept. 1, 2015, 3:49 p.m., Yusaku Sako wrote: > > This looks good. We can commit this, but let's have two follow-up actions. > > * Create a JIRA to add unit tests for all different scenarios mentioned. > > * Create a JIRA for making the HDFS username portion of the checkpoint > > command de

[jira] [Updated] (AMBARI-12965) Selection of SQLA should warn user that it is supported only for HDP-2.3.2 and beyond

[ https://issues.apache.org/jira/browse/AMBARI-12965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-12965: Attachment: before_patch.png after_patch.png > Selection of SQLA should wa

[jira] [Updated] (AMBARI-12965) Selection of SQLA should warn user that it is supported only for HDP-2.3.2 and beyond

[ https://issues.apache.org/jira/browse/AMBARI-12965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-12965: Attachment: AMBARI-12965.patch > Selection of SQLA should warn user that it is supported o

Re: Review Request 37979: Prompt user to save checkpoint before shutdown if last checkpoint is too old

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37979/#review97357 --- Ship it! This looks good. We can commit this, but let's have two f

[jira] [Created] (AMBARI-12965) Selection of SQLA should warn user that it is supported only for HDP-2.3.2 and beyond

Jaimin D Jetly created AMBARI-12965: --- Summary: Selection of SQLA should warn user that it is supported only for HDP-2.3.2 and beyond Key: AMBARI-12965 URL: https://issues.apache.org/jira/browse/AMBARI-12965

[jira] [Updated] (AMBARI-12931) Ambari shows "Corrupted Blocks" but it is "Corrupted replica"

[ https://issues.apache.org/jira/browse/AMBARI-12931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-12931: -- Attachment: AMBARI-12931.v1.patch > Ambari shows "Corrupted Blocks" but it is "Corrupted repli

[jira] [Created] (AMBARI-12964) change log4j.xml file name in atlas service definition to atlas-log4j.xml

Jonathan Maron created AMBARI-12964: --- Summary: change log4j.xml file name in atlas service definition to atlas-log4j.xml Key: AMBARI-12964 URL: https://issues.apache.org/jira/browse/AMBARI-12964 Pro

[jira] [Commented] (AMBARI-12963) Exceptions in ambari-server.log after ambari-server reset

[ https://issues.apache.org/jira/browse/AMBARI-12963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726129#comment-14726129 ] Hudson commented on AMBARI-12963: - SUCCESS: Integrated in Ambari-branch-2.1 #459 (See [

[jira] [Commented] (AMBARI-12963) Exceptions in ambari-server.log after ambari-server reset

[ https://issues.apache.org/jira/browse/AMBARI-12963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726117#comment-14726117 ] Hudson commented on AMBARI-12963: - FAILURE: Integrated in Ambari-trunk-Commit #3366 (See

[jira] [Updated] (AMBARI-12931) Ambari shows "Corrupted Blocks" but it is "Corrupted replica"

[ https://issues.apache.org/jira/browse/AMBARI-12931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-12931: -- Attachment: AMBARI-12931.patch > Ambari shows "Corrupted Blocks" but it is "Corrupted replica"

[jira] [Updated] (AMBARI-12931) Ambari shows "Corrupted Blocks" but it is "Corrupted replica"

[ https://issues.apache.org/jira/browse/AMBARI-12931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-12931: -- Attachment: (was: AMBARI-12931.patch) > Ambari shows "Corrupted Blocks" but it is "Corrupt

[jira] [Commented] (AMBARI-12940) SQLA: add property validation check for BP oozie/hive, about SQLA should be available only for stack 2.3+

[ https://issues.apache.org/jira/browse/AMBARI-12940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725871#comment-14725871 ] Hadoop QA commented on AMBARI-12940: {color:red}-1 overall{color}. Here are the res

[jira] [Resolved] (AMBARI-12963) Exceptions in ambari-server.log after ambari-server reset

[ https://issues.apache.org/jira/browse/AMBARI-12963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myroslav Papirkovskyy resolved AMBARI-12963. Resolution: Fixed Pushed to trunk and branch-2.1 > Exceptions in ambari-s

[jira] [Created] (AMBARI-12963) Exceptions in ambari-server.log after ambari-server reset

Myroslav Papirkovskyy created AMBARI-12963: -- Summary: Exceptions in ambari-server.log after ambari-server reset Key: AMBARI-12963 URL: https://issues.apache.org/jira/browse/AMBARI-12963 Projec

[jira] [Commented] (AMBARI-12962) New ambari-agent logging infra makes it difficult to attach a log4j appender

[ https://issues.apache.org/jira/browse/AMBARI-12962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725838#comment-14725838 ] Hudson commented on AMBARI-12962: - SUCCESS: Integrated in Ambari-trunk-Commit #3365 (See

[jira] [Commented] (AMBARI-12960) UX: after click Override for property was opened another tab (Settings instead Advanced)

[ https://issues.apache.org/jira/browse/AMBARI-12960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725835#comment-14725835 ] Hudson commented on AMBARI-12960: - SUCCESS: Integrated in Ambari-trunk-Commit #3365 (See

[jira] [Commented] (AMBARI-12944) Make it configurable to select which DB type is the default Ambari DB

[ https://issues.apache.org/jira/browse/AMBARI-12944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725837#comment-14725837 ] Hudson commented on AMBARI-12944: - SUCCESS: Integrated in Ambari-trunk-Commit #3365 (See

[jira] [Commented] (AMBARI-12920) “Oozie Quick links" in Ambari points to incorrect URL after enabling SSL

[ https://issues.apache.org/jira/browse/AMBARI-12920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725836#comment-14725836 ] Hudson commented on AMBARI-12920: - SUCCESS: Integrated in Ambari-trunk-Commit #3365 (See

[jira] [Commented] (AMBARI-12961) Need a robust check for the existence of a package

[ https://issues.apache.org/jira/browse/AMBARI-12961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725839#comment-14725839 ] Hudson commented on AMBARI-12961: - SUCCESS: Integrated in Ambari-trunk-Commit #3365 (See

[jira] [Commented] (AMBARI-12944) Make it configurable to select which DB type is the default Ambari DB

[ https://issues.apache.org/jira/browse/AMBARI-12944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725800#comment-14725800 ] Hudson commented on AMBARI-12944: - FAILURE: Integrated in Ambari-branch-2.1 #458 (See [

[jira] [Commented] (AMBARI-12958) SQLA: when "db name" for hive/oozie changed, "jdbc class" changes too so recommendations should be called

[ https://issues.apache.org/jira/browse/AMBARI-12958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725798#comment-14725798 ] Hudson commented on AMBARI-12958: - FAILURE: Integrated in Ambari-branch-2.1 #458 (See [

[jira] [Commented] (AMBARI-12962) New ambari-agent logging infra makes it difficult to attach a log4j appender

[ https://issues.apache.org/jira/browse/AMBARI-12962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725801#comment-14725801 ] Hudson commented on AMBARI-12962: - FAILURE: Integrated in Ambari-branch-2.1 #458 (See [

[jira] [Commented] (AMBARI-12960) UX: after click Override for property was opened another tab (Settings instead Advanced)

[ https://issues.apache.org/jira/browse/AMBARI-12960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725797#comment-14725797 ] Hudson commented on AMBARI-12960: - FAILURE: Integrated in Ambari-branch-2.1 #458 (See [

[jira] [Commented] (AMBARI-12920) “Oozie Quick links" in Ambari points to incorrect URL after enabling SSL

[ https://issues.apache.org/jira/browse/AMBARI-12920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725799#comment-14725799 ] Hudson commented on AMBARI-12920: - FAILURE: Integrated in Ambari-branch-2.1 #458 (See [

Re: Review Request 37984: Stop-and-Start Upgrade: DB Schema Changes

> On Sept. 1, 2015, 8:49 a.m., Dmitro Lisnichenko wrote: > > ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java, > > line 1192 > > > > > > Should I change my patch for moving out

[jira] [Updated] (AMBARI-12949) Downgrade fails with err: 500 status code received on POST method for API: /api/vi/clusters/mycluster/upgrades

[ https://issues.apache.org/jira/browse/AMBARI-12949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-12949: --- Description: I have a 4 node HDP 2.2 cluster where I created a configuration group to apply customized oozi

Re: Ambari 2.1 rolling upgrade not updating properties changed in a configuration group?

Yes, that is by design. Rolling Upgrade across a major stack version (such as HDP 2.2 -> 2.3) will merge configs as follows, Assume HDP 2.3 stack contains configs C1 ... Cn, with values V1 ... Vn. If HDP 2.2 contains any of those configs, and the user also modified the value, then Ambari will prese

Re: Possible Ambari 2.1 rollingupgrade/downgrade defect when using configuration groups?

Hi Di, This sounds like a backend bug during Downgrade and reverting to the original configs. Can you go ahead and create a Jira on Apache? Thanks, Alejandro On 8/31/15, 1:09 PM, "Di Li" wrote: >Hello > >Could someone please help to verify whether I have hit an rolling >upgrade/downgrade defec

Ambari 2.1 rolling upgrade not updating properties changed in a configuration group?

Hello all Is this bydesign that the rolling upgrade doesn't apply property changes to the properties overridden in the configuration group? On my 4 node cluster, I created a configuration group to apply some custom properties values in oozie-site.xml for the Oozie server only. After rolling up

Re: Review Request 37953: SQLA: add property validation check for BP oozie/hive, about SQLA should be available only for stack 2.3+

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37953/#review97301 --- Ship it! The basic change looks ok to me, but unit tests should be

Re: Review Request 37953: SQLA: add property validation check for BP oozie/hive, about SQLA should be available only for stack 2.3+

> On Вер. 1, 2015, 4:35 після полудня, Jayush Luniya wrote: > > ambari-server/src/main/java/org/apache/ambari/server/topology/BlueprintValidatorImpl.java, > > line 107 > > > > > > Shouldnt this be 2.3.2.0? No. 2.

Re: Review Request 37953: SQLA: add property validation check for BP oozie/hive, about SQLA should be available only for stack 2.3+

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37953/#review97299 --- ambari-server/src/main/java/org/apache/ambari/server/topology/Bluep

[jira] [Commented] (AMBARI-12957) FE: Do better handling for missed max or min jdk in stack definition.

[ https://issues.apache.org/jira/browse/AMBARI-12957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725654#comment-14725654 ] Hudson commented on AMBARI-12957: - ABORTED: Integrated in Ambari-trunk-Commit #3364 (See

[jira] [Commented] (AMBARI-12958) SQLA: when "db name" for hive/oozie changed, "jdbc class" changes too so recommendations should be called

[ https://issues.apache.org/jira/browse/AMBARI-12958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725653#comment-14725653 ] Hudson commented on AMBARI-12958: - ABORTED: Integrated in Ambari-trunk-Commit #3364 (See

[jira] [Commented] (AMBARI-12920) “Oozie Quick links" in Ambari points to incorrect URL after enabling SSL

[ https://issues.apache.org/jira/browse/AMBARI-12920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725618#comment-14725618 ] Hadoop QA commented on AMBARI-12920: {color:red}-1 overall{color}. Here are the res

[jira] [Commented] (AMBARI-12839) “Customize Services” section during Add Service wizard stuck with a loading icon

[ https://issues.apache.org/jira/browse/AMBARI-12839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725611#comment-14725611 ] Hudson commented on AMBARI-12839: - SUCCESS: Integrated in Ambari-branch-2.1 #457 (See [

[jira] [Commented] (AMBARI-12956) Host Checks: should not warn on nagios, ganglia or puppet packages

[ https://issues.apache.org/jira/browse/AMBARI-12956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725613#comment-14725613 ] Hudson commented on AMBARI-12956: - SUCCESS: Integrated in Ambari-branch-2.1 #457 (See [

[jira] [Commented] (AMBARI-12959) FE: Server overloaded with POST calls after changing config group

[ https://issues.apache.org/jira/browse/AMBARI-12959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725614#comment-14725614 ] Hadoop QA commented on AMBARI-12959: {color:red}-1 overall{color}. Here are the res

[jira] [Commented] (AMBARI-12957) FE: Do better handling for missed max or min jdk in stack definition.

[ https://issues.apache.org/jira/browse/AMBARI-12957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725612#comment-14725612 ] Hudson commented on AMBARI-12957: - SUCCESS: Integrated in Ambari-branch-2.1 #457 (See [

Re: Review Request 37953: SQLA: add property validation check for BP oozie/hive, about SQLA should be available only for stack 2.3+

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37953/#review97293 --- Ship it! Ship It! - Sumit Mohanty On Sept. 1, 2015, 3:40 p.m., V

[jira] [Commented] (AMBARI-12916) Make API server hostname for views configurable

[ https://issues.apache.org/jira/browse/AMBARI-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725596#comment-14725596 ] Hadoop QA commented on AMBARI-12916: {color:red}-1 overall{color}. Here are the res

[jira] [Resolved] (AMBARI-12944) Make it configurable to select which DB type is the default Ambari DB

[ https://issues.apache.org/jira/browse/AMBARI-12944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myroslav Papirkovskyy resolved AMBARI-12944. Resolution: Fixed Pushed to trunk and branch-2.1 > Make it configurable t

[jira] [Updated] (AMBARI-12940) SQLA: add property validation check for BP oozie/hive, about SQLA should be available only for stack 2.3+

[ https://issues.apache.org/jira/browse/AMBARI-12940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-12940: --- Attachment: AMBARI-12940.patch > SQLA: add property validation check for BP oozie/hi

Re: Review Request 37953: SQLA: add property validation check for BP oozie/hive, about SQLA should be available only for stack 2.3+

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37953/ --- (Updated Вер. 1, 2015, 3:40 після полудня) Review request for Ambari, Jayush Lu

[jira] [Updated] (AMBARI-12940) SQLA: add property validation check for BP oozie/hive, about SQLA should be available only for stack 2.3+

[ https://issues.apache.org/jira/browse/AMBARI-12940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-12940: --- Attachment: (was: AMBARI-12940.patch) > SQLA: add property validation check for

[jira] [Commented] (AMBARI-12920) “Oozie Quick links" in Ambari points to incorrect URL after enabling SSL

[ https://issues.apache.org/jira/browse/AMBARI-12920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725561#comment-14725561 ] Andrii Babiichuk commented on AMBARI-12920: --- +1 for the patch > “Oozie Quick

[jira] [Reopened] (AMBARI-12920) “Oozie Quick links" in Ambari points to incorrect URL after enabling SSL

[ https://issues.apache.org/jira/browse/AMBARI-12920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reopened AMBARI-12920: -- Reopening to make additional commit, that will also cover cases when we have oozi

[jira] [Updated] (AMBARI-12920) “Oozie Quick links" in Ambari points to incorrect URL after enabling SSL

[ https://issues.apache.org/jira/browse/AMBARI-12920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-12920: - Attachment: AMBARI-12920_Additional.patch > “Oozie Quick links" in Ambari points

[jira] [Commented] (AMBARI-12960) UX: after click Override for property was opened another tab (Settings instead Advanced)

[ https://issues.apache.org/jira/browse/AMBARI-12960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725514#comment-14725514 ] Andrii Babiichuk commented on AMBARI-12960: --- +1 for the patch > UX: after cli

[jira] [Resolved] (AMBARI-12962) New ambari-agent logging infra makes it difficult to attach a log4j appender

[ https://issues.apache.org/jira/browse/AMBARI-12962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk resolved AMBARI-12962. -- Resolution: Fixed Committed to trunk and branch-2.1 > New ambari-agent logging infra

Re: Review Request 38008: New ambari-agent logging infra makes it difficult to attach a log4j appender

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/38008/#review97289 --- Ship it! Ship It! - Dmitro Lisnichenko On Sept. 1, 2015, 3:01 p.

Review Request 38008: New ambari-agent logging infra makes it difficult to attach a log4j appender

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/38008/ --- Review request for Ambari and Dmitro Lisnichenko. Bugs: AMBARI-12962 https:

[jira] [Created] (AMBARI-12962) New ambari-agent logging infra makes it difficult to attach a log4j appender

Andrew Onischuk created AMBARI-12962: Summary: New ambari-agent logging infra makes it difficult to attach a log4j appender Key: AMBARI-12962 URL: https://issues.apache.org/jira/browse/AMBARI-12962

[jira] [Updated] (AMBARI-12961) Need a robust check for the existence of a package

[ https://issues.apache.org/jira/browse/AMBARI-12961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-12961: - Fix Version/s: (was: 2.1.2) 2.2.0 > Need a robust check for the e

[jira] [Resolved] (AMBARI-12961) Need a robust check for the existence of a package

[ https://issues.apache.org/jira/browse/AMBARI-12961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk resolved AMBARI-12961. -- Resolution: Fixed Committed to trunk > Need a robust check for the existence of a pac

Re: Review Request 38007: Need a robust check for the existence of a package

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/38007/#review97287 --- Ship it! Ship It! - Dmitro Lisnichenko On Sept. 1, 2015, 2:44 p.

Review Request 38007: Need a robust check for the existence of a package

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/38007/ --- Review request for Ambari and Dmitro Lisnichenko. Bugs: AMBARI-12961 https:

[jira] [Created] (AMBARI-12961) Need a robust check for the existence of a package

Andrew Onischuk created AMBARI-12961: Summary: Need a robust check for the existence of a package Key: AMBARI-12961 URL: https://issues.apache.org/jira/browse/AMBARI-12961 Project: Ambari

[jira] [Updated] (AMBARI-12960) UX: after click Override for property was opened another tab (Settings instead Advanced)

[ https://issues.apache.org/jira/browse/AMBARI-12960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-12960: - Attachment: AMBARI-12960.patch > UX: after click Override for property was opene

[jira] [Commented] (AMBARI-12955) First adding hosts to created host group is not possible - no any host is displayed

[ https://issues.apache.org/jira/browse/AMBARI-12955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725441#comment-14725441 ] Hudson commented on AMBARI-12955: - FAILURE: Integrated in Ambari-trunk-Commit #3363 (See

[jira] [Commented] (AMBARI-12839) “Customize Services” section during Add Service wizard stuck with a loading icon

[ https://issues.apache.org/jira/browse/AMBARI-12839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725440#comment-14725440 ] Hudson commented on AMBARI-12839: - FAILURE: Integrated in Ambari-trunk-Commit #3363 (See

[jira] [Commented] (AMBARI-12956) Host Checks: should not warn on nagios, ganglia or puppet packages

[ https://issues.apache.org/jira/browse/AMBARI-12956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725442#comment-14725442 ] Hudson commented on AMBARI-12956: - FAILURE: Integrated in Ambari-trunk-Commit #3363 (See

[jira] [Created] (AMBARI-12960) UX: after click Override for property was opened another tab (Settings instead Advanced)

Antonenko Alexander created AMBARI-12960: Summary: UX: after click Override for property was opened another tab (Settings instead Advanced) Key: AMBARI-12960 URL: https://issues.apache.org/jira/browse/AMBA

[jira] [Commented] (AMBARI-12958) SQLA: when "db name" for hive/oozie changed, "jdbc class" changes too so recommendations should be called

[ https://issues.apache.org/jira/browse/AMBARI-12958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725401#comment-14725401 ] Andrii Tkach commented on AMBARI-12958: --- +1 for the patch > SQLA: when "db name"

[jira] [Updated] (AMBARI-12958) SQLA: when "db name" for hive/oozie changed, "jdbc class" changes too so recommendations should be called

[ https://issues.apache.org/jira/browse/AMBARI-12958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-12958: -- Attachment: AMBARI-12958.patch > SQLA: when "db name" for hive/oozie changed, "jdbc cl

  1   2   >