[jira] [Commented] (AMBARI-21377) Add HiveVectorizedORC and JDBC profiles to pxf-profiles.xml config file

[Lav Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16070623#comment-16070623
 ] 

Lav Jain commented on AMBARI-21377:
---

commit 5e60ea6462183984a13e09ebc8c1d22f95c86f8f (HEAD -> branch-2.5, 
upstream/branch-2.5)
Author: lavjain 
Date:   Fri Jun 30 12:38:38 2017 -0700


> Add HiveVectorizedORC and JDBC profiles to pxf-profiles.xml config file 
> 
>
> Key: AMBARI-21377
> URL: https://issues.apache.org/jira/browse/AMBARI-21377
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: 2.5.2
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: trunk, 2.5.2
>
> Attachments: AMBARI-21377.txt
>
>
> To reflect changes introduced in 
> https://issues.apache.org/jira/browse/HAWQ-1492 and 
> https://issues.apache.org/jira/browse/HAWQ-1446



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21377) Add HiveVectorizedORC and JDBC profiles to pxf-profiles.xml config file

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-21377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-21377:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Add HiveVectorizedORC and JDBC profiles to pxf-profiles.xml config file 
> 
>
> Key: AMBARI-21377
> URL: https://issues.apache.org/jira/browse/AMBARI-21377
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: 2.5.2
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: trunk, 2.5.2
>
> Attachments: AMBARI-21377.txt
>
>
> To reflect changes introduced in 
> https://issues.apache.org/jira/browse/HAWQ-1492 and 
> https://issues.apache.org/jira/browse/HAWQ-1446



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-21377) Add HiveVectorizedORC and JDBC profiles to pxf-profiles.xml config file

[Lav Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-21377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16070622#comment-16070622
 ] 

Lav Jain commented on AMBARI-21377:
---

commit 9a17ca78d9c4e4e09123f1640b8f521f246a8b5f (HEAD -> trunk, upstream/trunk)
Author: lavjain 
Date:   Fri Jun 30 12:34:45 2017 -0700


> Add HiveVectorizedORC and JDBC profiles to pxf-profiles.xml config file 
> 
>
> Key: AMBARI-21377
> URL: https://issues.apache.org/jira/browse/AMBARI-21377
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: 2.5.2
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: trunk, 2.5.2
>
> Attachments: AMBARI-21377.txt
>
>
> To reflect changes introduced in 
> https://issues.apache.org/jira/browse/HAWQ-1492 and 
> https://issues.apache.org/jira/browse/HAWQ-1446



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21377) Add HiveVectorizedORC and JDBC profiles to pxf-profiles.xml config file

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-21377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-21377:
--
Attachment: AMBARI-21377.txt

> Add HiveVectorizedORC and JDBC profiles to pxf-profiles.xml config file 
> 
>
> Key: AMBARI-21377
> URL: https://issues.apache.org/jira/browse/AMBARI-21377
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: 2.5.2
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: trunk, 2.5.2
>
> Attachments: AMBARI-21377.txt
>
>
> To reflect changes introduced in 
> https://issues.apache.org/jira/browse/HAWQ-1492 and 
> https://issues.apache.org/jira/browse/HAWQ-1446



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21377) Add HiveVectorizedORC and JDBC profiles to pxf-profiles.xml config file

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-21377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-21377:
--
Fix Version/s: 2.5.2
   trunk
   Status: Patch Available  (was: Open)

> Add HiveVectorizedORC and JDBC profiles to pxf-profiles.xml config file 
> 
>
> Key: AMBARI-21377
> URL: https://issues.apache.org/jira/browse/AMBARI-21377
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: 2.5.2
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: trunk, 2.5.2
>
> Attachments: AMBARI-21377.txt
>
>
> To reflect changes introduced in 
> https://issues.apache.org/jira/browse/HAWQ-1492 and 
> https://issues.apache.org/jira/browse/HAWQ-1446



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (AMBARI-21377) Add HiveVectorizedORC and JDBC profiles to pxf-profiles.xml config file

[Lav Jain (JIRA)]

Lav Jain created AMBARI-21377:
-

 Summary: Add HiveVectorizedORC and JDBC profiles to 
pxf-profiles.xml config file 
 Key: AMBARI-21377
 URL: https://issues.apache.org/jira/browse/AMBARI-21377
 Project: Ambari
  Issue Type: Improvement
  Components: stacks
Affects Versions: 2.5.2
Reporter: Lav Jain


To reflect changes introduced in 
https://issues.apache.org/jira/browse/HAWQ-1492 and 
https://issues.apache.org/jira/browse/HAWQ-1446





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (AMBARI-21377) Add HiveVectorizedORC and JDBC profiles to pxf-profiles.xml config file

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-21377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain reassigned AMBARI-21377:
-

Assignee: Lav Jain

> Add HiveVectorizedORC and JDBC profiles to pxf-profiles.xml config file 
> 
>
> Key: AMBARI-21377
> URL: https://issues.apache.org/jira/browse/AMBARI-21377
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: 2.5.2
>Reporter: Lav Jain
>Assignee: Lav Jain
>
> To reflect changes introduced in 
> https://issues.apache.org/jira/browse/HAWQ-1492 and 
> https://issues.apache.org/jira/browse/HAWQ-1446



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-20547) Update pxf-profiles.xml config file comments for all Hive-related profiles in PXF

[Lav Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-20547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15940952#comment-15940952
 ] 

Lav Jain commented on AMBARI-20547:
---

+1 LGTM

> Update pxf-profiles.xml config file comments for all Hive-related profiles in 
> PXF
> -
>
> Key: AMBARI-20547
> URL: https://issues.apache.org/jira/browse/AMBARI-20547
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-20547.patch
>
>
> To reflect changes introduced in 
> https://issues.apache.org/jira/browse/HAWQ-1402



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-17679) HAWQ stack: identify properties added to Ambari-2.4.0 and mark appropriate ones to not get added during Ambari upgrade

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-17679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-17679:
--
Priority: Major  (was: Critical)

> HAWQ stack: identify properties added to Ambari-2.4.0 and mark appropriate 
> ones to not get added during Ambari upgrade
> --
>
> Key: AMBARI-17679
> URL: https://issues.apache.org/jira/browse/AMBARI-17679
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Lav Jain
> Fix For: trunk
>
>
> For any HAWQ config properties that need not be added upon Ambari upgrade, 
> set on-ambari-upgrade attribute add to false.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-17679) HAWQ stack: identify properties added to Ambari-2.4.0 and mark appropriate ones to not get added during Ambari upgrade

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-17679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-17679:
--
Fix Version/s: (was: 2.5.0)
   trunk

> HAWQ stack: identify properties added to Ambari-2.4.0 and mark appropriate 
> ones to not get added during Ambari upgrade
> --
>
> Key: AMBARI-17679
> URL: https://issues.apache.org/jira/browse/AMBARI-17679
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Lav Jain
> Fix For: trunk
>
>
> For any HAWQ config properties that need not be added upon Ambari upgrade, 
> set on-ambari-upgrade attribute add to false.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-19805) Add outputFormat attribute to all PXF Hive-related profiles

[Lav Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-19805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849076#comment-15849076
 ] 

Lav Jain commented on AMBARI-19805:
---

+1 for the patch

> Add outputFormat attribute to all PXF Hive-related profiles
> ---
>
> Key: AMBARI-19805
> URL: https://issues.apache.org/jira/browse/AMBARI-19805
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19805.patch
>
>
> There was new attribute outputFormat introduced in 
> https://issues.apache.org/jira/browse/HAWQ-1228, which needs to be reflected 
> in PXF as a common service.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-18725) Ambari Database Check failed to Complete Error

[Lav Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-18725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15615934#comment-15615934
 ] 

Lav Jain commented on AMBARI-18725:
---

[~rlevas] This is happening on a clean install with both Ambari 2.4.2 as well 
as Ambari 2.5.0 on Centos6

> Ambari Database Check failed to Complete Error
> --
>
> Key: AMBARI-18725
> URL: https://issues.apache.org/jira/browse/AMBARI-18725
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.5.0, 2.4.2
>Reporter: Matt
>Assignee: Robert Levas
>Priority: Blocker
> Fix For: 2.5.0, 2.4.2
>
>
> Built Ambari from branch-2.4, branch-2.5 and trunk. All the builds have the 
> same issue when the start command is run.
> {code}> ambari-server start
> Using python  /usr/bin/python
> Starting ambari-server
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> No errors were found.
> ERROR: Exiting with exit code 1.
> REASON: Database check failed to complete. Please check 
> /var/log/ambari-server/ambari-server.log and 
> /var/log/ambari-server/ambari-server-check-database.log for more 
> information.{code}
> The database.log says {code}Error preallocating sequence numbers{code}
> Nothing suspicious on ambari-server.log.
> Log file ambari-server-check-database.log attached with this JIRA for 
> reference.
> *Update*
> Reverting 
> https://github.com/apache/ambari/commit/b632b33bc35afc5a01354e8916fdcdf698e49e19
>  on a local copy of branch-2.4 fixed the issue on branch-2.4 build
> Reverting 
> https://github.com/apache/ambari/commit/49f58e8402b543875c61f8d74a052bd6cd45a788
>  on a local copy of branch-2.5 fixed the issue on branch-2.5 build



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18337) Syntax Error in Ambari HAWQ Unit test with Python 2.6

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-18337:
--
   Resolution: Fixed
Fix Version/s: 2.4.2
   2.5.0
   trunk
   Status: Resolved  (was: Patch Available)

> Syntax Error in Ambari HAWQ Unit test with Python 2.6
> -
>
> Key: AMBARI-18337
> URL: https://issues.apache.org/jira/browse/AMBARI-18337
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
> Environment: CentOS6, Python 2.6
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Fix For: trunk, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18337.patch
>
>
> With Python 2.6, {code} {"A", "B"}  {code} syntax isn't allowed.
> Ref. https://docs.python.org/2/library/stdtypes.html#set-types-set-frozenset
> {code}
> As of Python 2.7, non-empty sets (not frozensets) can be created by placing a 
> comma-separated list of elements within braces, for example: {'jack', 
> 'sjoerd'}, in addition to the set constructor.
> {code}
> Error
> {code}
> Traceback (most recent call last):
>   File "unitTests.py", line 129, in stack_test_executor
> modules]
>   File "/usr/lib64/python2.6/unittest.py", line 575, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
>   File 
> "/tmp/ambari/ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py",
>  li
> ne 646
> self.assertFalse({'HAWQMASTER', 'HAWQSTANDBY'}.issubset(hostComponents))
>   ^
> SyntaxError: invalid syntax
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18337) Syntax Error in Ambari HAWQ Unit test with Python 2.6

[Lav Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-18337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15507874#comment-15507874
 ] 

Lav Jain commented on AMBARI-18337:
---

Committed to branch-2.4 (0a992d667ab485050fb14984310e39020eb6b8b7), branch-2.5 
(ef837ba141c74b1db2497217995205e5d9340432) and trunk 
(3b30de0a8ad939768e9194fb63ef19f07eaabaee)



> Syntax Error in Ambari HAWQ Unit test with Python 2.6
> -
>
> Key: AMBARI-18337
> URL: https://issues.apache.org/jira/browse/AMBARI-18337
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
> Environment: CentOS6, Python 2.6
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Fix For: trunk, 2.5.0, 2.4.2
>
> Attachments: AMBARI-18337.patch
>
>
> With Python 2.6, {code} {"A", "B"}  {code} syntax isn't allowed.
> Ref. https://docs.python.org/2/library/stdtypes.html#set-types-set-frozenset
> {code}
> As of Python 2.7, non-empty sets (not frozensets) can be created by placing a 
> comma-separated list of elements within braces, for example: {'jack', 
> 'sjoerd'}, in addition to the set constructor.
> {code}
> Error
> {code}
> Traceback (most recent call last):
>   File "unitTests.py", line 129, in stack_test_executor
> modules]
>   File "/usr/lib64/python2.6/unittest.py", line 575, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
>   File 
> "/tmp/ambari/ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py",
>  li
> ne 646
> self.assertFalse({'HAWQMASTER', 'HAWQSTANDBY'}.issubset(hostComponents))
>   ^
> SyntaxError: invalid syntax
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15538) Support service-specific repo for add-on services

[Lav Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494027#comment-15494027
 ] 

Lav Jain commented on AMBARI-15538:
---

[~jluniya] I do not see this JIRA being committed to 2.4.2 yet (only committed 
to 2.5 and trunk) .

> Support service-specific repo for add-on services
> -
>
> Key: AMBARI-15538
> URL: https://issues.apache.org/jira/browse/AMBARI-15538
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0, 2.2.0, 2.4.0
>Reporter: Jayush Luniya
>Assignee: Balázs Bence Sári
>Priority: Critical
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-15538-custom-repos-patch6-branch-25.diff, 
> AMBARI-15538-custom-repos-patch6-trunk.diff
>
>
> The approach for custom-services to specify their own repo location will be 
> to provide a {{/repos/repoinfo.xml}} inside the stack-version they will be 
> in. This repo file will be loaded by Ambari during startup into the 
> {{/api/v1/stacks/HDP/versions/2.4/repository_versions}} repos. *Service repo 
> files have a restriction that their (repo-name, base-url) locations should be 
> unique and not conflict*. When conflicts do occur, they will not be loaded 
> into the stacks model.
> Now the management-pack will provide such repos/ folder in 
> {{mpacks/custom-services/8.0.0/repos}} which will be linked into the stacks/ 
> folder.
> {{ambari/ambari-server/src/main/resources/stacks/HDP/2.3/services/SERVICE_NAME/repos
>  -> mpacks/custom-services/8.0.0/repos}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18297) Add View for Apache HAWQ

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-18297:
--
Priority: Major  (was: Minor)

[~sumitmohanty]
This has been a major feature for HAWQ and folks at Pivotal have been working 
on it for the past few months. Also, it is part of contrib folder, so should 
not affect the main release till release engineering enables it.

> Add View for Apache HAWQ
> 
>
> Key: AMBARI-18297
> URL: https://issues.apache.org/jira/browse/AMBARI-18297
> Project: Ambari
>  Issue Type: New Feature
>  Components: contrib
>Affects Versions: trunk
>Reporter: Matt
>Assignee: Stuart Pollock
> Fix For: trunk
>
> Attachments: AMBARI-18297-orig-binary.patch, AMBARI-18297-orig.patch, 
> AMBARI-18297-v1-binary.patch
>
>
> Add initial code for HAWQ View under contrib/views



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17717) Ambari should have a script to add new repository and service to existing stack

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-17717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-17717:
--
Status: Open  (was: Patch Available)

The patch was not favored by Ambari community. Will explore management packs as 
Jayush requested.

> Ambari should have a script to add new repository and service to existing 
> stack
> ---
>
> Key: AMBARI-17717
> URL: https://issues.apache.org/jira/browse/AMBARI-17717
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk
>
> Attachments: AMBARI-17717.patch
>
>
> Ambari should have a script that users can run to add a custom service and 
> repository to the stack or an existing cluster.
> {code}
> Lavs-MacBook-Pro:scripts ljain$ ./add_common_service.py -h
> Usage: add_common_service.py [options]
> Options:
>   -h, --helpshow this help message and exit
>   -u USER, --user=USER  Ambari login username (Required)
>   -p PASSWORD, --password=PASSWORD
> Ambari login password. Providing password through
> command line is not recommended. The script prompts
> for the password.
>   -t STACK, --stack=STACK
> Stack Name and Version to be added (Required).(Eg:
> HDP-2.4 or HDP-2.5)
>   -s SERVICE, --service=SERVICE
> Service Name and Version to be added.(Eg: HAWQ/2.0.0
> or PXF/3.0.0)
>   -r REPOURL, --repourl=REPOURL
> Repository URL which points to the rpm packages
>   -i REPOID, --repoid=REPOID
> Repository ID of the new repository
>   -o OSTYPE, --ostype=OSTYPE
> OS for the new repository (Eg: redhat6)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17717) Ambari should have a script to add new repository and service to existing stack

[Lav Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-17717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423262#comment-15423262
 ] 

Lav Jain commented on AMBARI-17717:
---

[~Tim Thorpe]

Please feel free to update/close this Jira when your script has been finalized.

> Ambari should have a script to add new repository and service to existing 
> stack
> ---
>
> Key: AMBARI-17717
> URL: https://issues.apache.org/jira/browse/AMBARI-17717
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk
>
> Attachments: AMBARI-17717.patch
>
>
> Ambari should have a script that users can run to add a custom service and 
> repository to the stack or an existing cluster.
> {code}
> Lavs-MacBook-Pro:scripts ljain$ ./add_common_service.py -h
> Usage: add_common_service.py [options]
> Options:
>   -h, --helpshow this help message and exit
>   -u USER, --user=USER  Ambari login username (Required)
>   -p PASSWORD, --password=PASSWORD
> Ambari login password. Providing password through
> command line is not recommended. The script prompts
> for the password.
>   -t STACK, --stack=STACK
> Stack Name and Version to be added (Required).(Eg:
> HDP-2.4 or HDP-2.5)
>   -s SERVICE, --service=SERVICE
> Service Name and Version to be added.(Eg: HAWQ/2.0.0
> or PXF/3.0.0)
>   -r REPOURL, --repourl=REPOURL
> Repository URL which points to the rpm packages
>   -i REPOID, --repoid=REPOID
> Repository ID of the new repository
>   -o OSTYPE, --ostype=OSTYPE
> OS for the new repository (Eg: redhat6)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17938) Ambari should not recursively chown for HAWQ hdfs upon every start

[Lav Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-17938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423246#comment-15423246
 ] 

Lav Jain commented on AMBARI-17938:
---

Confirmed. Thanks [~jluniya] for taking care of this.

> Ambari should not recursively chown for HAWQ hdfs upon every start
> --
>
> Key: AMBARI-17938
> URL: https://issues.apache.org/jira/browse/AMBARI-17938
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
>Assignee: Lav Jain
>  Labels: performance
> Fix For: 2.4.0
>
> Attachments: AMBARI-17938.patch, AMBARI-17938.v2.patch, 
> AMBARI-17938.v3.patch
>
>
> This results in changing of owner even if the owner value is same. The 
> operation is very costly if there are a lot of subdirectories.
> The owner value only changes when you switch from regular mode to secure mode 
> and vice-versa.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18110) Ambari unit tests for HAWQ are not being called

[Lav Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-18110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419539#comment-15419539
 ] 

Lav Jain commented on AMBARI-18110:
---

BRANCH-2.4
commit 85c97e3a7f3db4d85fc01a82e7286c4c45fdb99a
Author: Lav Jain 
Fri, 12 Aug 2016 14:34:47 -0700 (14:34 -0700)

TRUNK
commit 5676cd0c946dc34468037b4996d5f1ce7fac20e0
Author: Lav Jain 
Fri, 12 Aug 2016 14:36:04 -0700 (14:36 -0700)

> Ambari unit tests for HAWQ are not being called
> ---
>
> Key: AMBARI-18110
> URL: https://issues.apache.org/jira/browse/AMBARI-18110
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-18110.patch, AMBARI-18110.v2.patch, 
> AMBARI-18110.v3.patch
>
>
> Ambari build jobs are not running the unit tests for HAWQ.
> HAWQ (and PXF) unit tests in the new common-services directory under test is 
> being ignored during maven's test phase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18110) Ambari unit tests for HAWQ are not being called

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-18110:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Ambari unit tests for HAWQ are not being called
> ---
>
> Key: AMBARI-18110
> URL: https://issues.apache.org/jira/browse/AMBARI-18110
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-18110.patch, AMBARI-18110.v2.patch, 
> AMBARI-18110.v3.patch
>
>
> Ambari build jobs are not running the unit tests for HAWQ.
> HAWQ (and PXF) unit tests in the new common-services directory under test is 
> being ignored during maven's test phase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18110) Ambari unit tests for HAWQ are not being called

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-18110:
--
Attachment: AMBARI-18110.v3.patch

> Ambari unit tests for HAWQ are not being called
> ---
>
> Key: AMBARI-18110
> URL: https://issues.apache.org/jira/browse/AMBARI-18110
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-18110.patch, AMBARI-18110.v2.patch, 
> AMBARI-18110.v3.patch
>
>
> Ambari build jobs are not running the unit tests for HAWQ.
> HAWQ (and PXF) unit tests in the new common-services directory under test is 
> being ignored during maven's test phase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18110) Ambari unit tests for HAWQ are not being called

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-18110:
--
Status: In Progress  (was: Patch Available)

> Ambari unit tests for HAWQ are not being called
> ---
>
> Key: AMBARI-18110
> URL: https://issues.apache.org/jira/browse/AMBARI-18110
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
> Fix For: 2.4.0
>
> Attachments: AMBARI-18110.patch, AMBARI-18110.v2.patch
>
>
> Ambari build jobs are not running the unit tests for HAWQ.
> HAWQ (and PXF) unit tests in the new common-services directory under test is 
> being ignored during maven's test phase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18110) Ambari unit tests for HAWQ are not being called

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-18110:
--
Fix Version/s: trunk
   Status: Patch Available  (was: In Progress)

> Ambari unit tests for HAWQ are not being called
> ---
>
> Key: AMBARI-18110
> URL: https://issues.apache.org/jira/browse/AMBARI-18110
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-18110.patch, AMBARI-18110.v2.patch
>
>
> Ambari build jobs are not running the unit tests for HAWQ.
> HAWQ (and PXF) unit tests in the new common-services directory under test is 
> being ignored during maven's test phase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18110) Ambari unit tests for HAWQ are not being called

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-18110:
--
Attachment: AMBARI-18110.v2.patch

> Ambari unit tests for HAWQ are not being called
> ---
>
> Key: AMBARI-18110
> URL: https://issues.apache.org/jira/browse/AMBARI-18110
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-18110.patch, AMBARI-18110.v2.patch
>
>
> Ambari build jobs are not running the unit tests for HAWQ.
> HAWQ (and PXF) unit tests in the new common-services directory under test is 
> being ignored during maven's test phase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (AMBARI-18110) Ambari unit tests for HAWQ are not being called

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain reassigned AMBARI-18110:
-

Assignee: Lav Jain

> Ambari unit tests for HAWQ are not being called
> ---
>
> Key: AMBARI-18110
> URL: https://issues.apache.org/jira/browse/AMBARI-18110
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-18110.patch, AMBARI-18110.v2.patch
>
>
> Ambari build jobs are not running the unit tests for HAWQ.
> HAWQ (and PXF) unit tests in the new common-services directory under test is 
> being ignored during maven's test phase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18110) Ambari unit tests for HAWQ are not being called

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-18110:
--
Fix Version/s: 2.4.0
   Status: Patch Available  (was: Open)

> Ambari unit tests for HAWQ are not being called
> ---
>
> Key: AMBARI-18110
> URL: https://issues.apache.org/jira/browse/AMBARI-18110
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
> Fix For: 2.4.0
>
> Attachments: AMBARI-18110.patch
>
>
> Ambari build jobs are not running the unit tests for HAWQ.
> HAWQ (and PXF) unit tests in the new common-services directory under test is 
> being ignored during maven's test phase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18110) Ambari unit tests for HAWQ are not being called

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-18110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-18110:
--
Attachment: AMBARI-18110.patch

> Ambari unit tests for HAWQ are not being called
> ---
>
> Key: AMBARI-18110
> URL: https://issues.apache.org/jira/browse/AMBARI-18110
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
> Attachments: AMBARI-18110.patch
>
>
> Ambari build jobs are not running the unit tests for HAWQ.
> HAWQ (and PXF) unit tests in the new common-services directory under test is 
> being ignored during maven's test phase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-18110) Ambari unit tests for HAWQ are not being called

[Lav Jain (JIRA)]

Lav Jain created AMBARI-18110:
-

 Summary: Ambari unit tests for HAWQ are not being called
 Key: AMBARI-18110
 URL: https://issues.apache.org/jira/browse/AMBARI-18110
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: trunk, 2.4.0
Reporter: Lav Jain


Ambari build jobs are not running the unit tests for HAWQ.

HAWQ (and PXF) unit tests in the new common-services directory under test is 
being ignored during maven's test phase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17938) Ambari should not recursively chown for HAWQ hdfs upon every start

[Lav Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-17938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15406659#comment-15406659
 ] 

Lav Jain commented on AMBARI-17938:
---

BRANCH 2.4

author  Lav Jain  
Wed, 3 Aug 2016 14:31:12 -0700 (14:31 -0700)
commit  516ec8663136a57e274f2fc85e7ae31a34c1ba63

TRUNK

author  Lav Jain  
Wed, 3 Aug 2016 14:33:13 -0700 (14:33 -0700)
commit  a90b7f7ccd9131463dbc49691f1e26f187d0aa09

> Ambari should not recursively chown for HAWQ hdfs upon every start
> --
>
> Key: AMBARI-17938
> URL: https://issues.apache.org/jira/browse/AMBARI-17938
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
>Assignee: Lav Jain
>  Labels: performance
> Fix For: 2.4.0
>
> Attachments: AMBARI-17938.patch, AMBARI-17938.v2.patch, 
> AMBARI-17938.v3.patch
>
>
> This results in changing of owner even if the owner value is same. The 
> operation is very costly if there are a lot of subdirectories.
> The owner value only changes when you switch from regular mode to secure mode 
> and vice-versa.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17938) Ambari should not recursively chown for HAWQ hdfs upon every start

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-17938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-17938:
--
Attachment: AMBARI-17938.v3.patch

> Ambari should not recursively chown for HAWQ hdfs upon every start
> --
>
> Key: AMBARI-17938
> URL: https://issues.apache.org/jira/browse/AMBARI-17938
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
>Assignee: Lav Jain
>  Labels: performance
> Fix For: 2.4.0
>
> Attachments: AMBARI-17938.patch, AMBARI-17938.v2.patch, 
> AMBARI-17938.v3.patch
>
>
> This results in changing of owner even if the owner value is same. The 
> operation is very costly if there are a lot of subdirectories.
> The owner value only changes when you switch from regular mode to secure mode 
> and vice-versa.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17938) Ambari should not recursively chown for HAWQ hdfs upon every start

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-17938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-17938:
--
Attachment: AMBARI-17938.v2.patch

> Ambari should not recursively chown for HAWQ hdfs upon every start
> --
>
> Key: AMBARI-17938
> URL: https://issues.apache.org/jira/browse/AMBARI-17938
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
>Assignee: Lav Jain
>  Labels: performance
> Fix For: 2.4.0
>
> Attachments: AMBARI-17938.patch, AMBARI-17938.v2.patch
>
>
> This results in changing of owner even if the owner value is same. The 
> operation is very costly if there are a lot of subdirectories.
> The owner value only changes when you switch from regular mode to secure mode 
> and vice-versa.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17937) Ambari install/init should create a new gpadmin database

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-17937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-17937:
--
   Resolution: Fixed
Fix Version/s: trunk
   Status: Resolved  (was: Patch Available)

> Ambari install/init should create a new gpadmin database
> 
>
> Key: AMBARI-17937
> URL: https://issues.apache.org/jira/browse/AMBARI-17937
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
>Assignee: Lav Jain
>Priority: Minor
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-17937.patch
>
>
> If you are logged in as gpadmin on the master and type in "psql" to connect 
> to the database, it will fail.  psql assumes you want to connect to the 
> database named "gpadmin" which matches your username. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17937) Ambari install/init should create a new gpadmin database

[Lav Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-17937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15406599#comment-15406599
 ] 

Lav Jain commented on AMBARI-17937:
---

BRANCH-2.4

commit 8138a9dbee872e1a5309fa929a678fb7ff806b98
Author: Lav Jain 
Wed, 3 Aug 2016 13:48:07 -0700 (13:48 -0700)

TRUNK

commit c2e9b465df3b3c175baf9048784f38dd486a14a6
Author: Lav Jain 
Wed, 3 Aug 2016 13:54:39 -0700 (13:54 -0700)

> Ambari install/init should create a new gpadmin database
> 
>
> Key: AMBARI-17937
> URL: https://issues.apache.org/jira/browse/AMBARI-17937
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
>Assignee: Lav Jain
>Priority: Minor
> Fix For: 2.4.0
>
> Attachments: AMBARI-17937.patch
>
>
> If you are logged in as gpadmin on the master and type in "psql" to connect 
> to the database, it will fail.  psql assumes you want to connect to the 
> database named "gpadmin" which matches your username. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17938) Ambari should not recursively chown for HAWQ hdfs upon every start

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-17938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-17938:
--
   Labels: performance  (was: )
Fix Version/s: 2.4.0
Affects Version/s: trunk
   Status: Patch Available  (was: Open)

> Ambari should not recursively chown for HAWQ hdfs upon every start
> --
>
> Key: AMBARI-17938
> URL: https://issues.apache.org/jira/browse/AMBARI-17938
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
>Assignee: Lav Jain
>  Labels: performance
> Fix For: 2.4.0
>
> Attachments: AMBARI-17938.patch
>
>
> This results in changing of owner even if the owner value is same. The 
> operation is very costly if there are a lot of subdirectories.
> The owner value only changes when you switch from regular mode to secure mode 
> and vice-versa.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17938) Ambari should not recursively chown for HAWQ hdfs upon every start

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-17938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-17938:
--
Attachment: AMBARI-17938.patch

> Ambari should not recursively chown for HAWQ hdfs upon every start
> --
>
> Key: AMBARI-17938
> URL: https://issues.apache.org/jira/browse/AMBARI-17938
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Lav Jain
>Assignee: Lav Jain
> Attachments: AMBARI-17938.patch
>
>
> This results in changing of owner even if the owner value is same. The 
> operation is very costly if there are a lot of subdirectories.
> The owner value only changes when you switch from regular mode to secure mode 
> and vice-versa.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17937) Ambari install/init should create a new gpadmin database

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-17937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-17937:
--
Affects Version/s: trunk
   Status: Patch Available  (was: Open)

> Ambari install/init should create a new gpadmin database
> 
>
> Key: AMBARI-17937
> URL: https://issues.apache.org/jira/browse/AMBARI-17937
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
>Assignee: Lav Jain
>Priority: Minor
> Fix For: 2.4.0
>
> Attachments: AMBARI-17937.patch
>
>
> If you are logged in as gpadmin on the master and type in "psql" to connect 
> to the database, it will fail.  psql assumes you want to connect to the 
> database named "gpadmin" which matches your username. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-17938) Ambari should not recursively chown for HAWQ hdfs upon every start

[Lav Jain (JIRA)]

Lav Jain created AMBARI-17938:
-

 Summary: Ambari should not recursively chown for HAWQ hdfs upon 
every start
 Key: AMBARI-17938
 URL: https://issues.apache.org/jira/browse/AMBARI-17938
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Lav Jain
Assignee: Lav Jain


This results in changing of owner even if the owner value is same. The 
operation is very costly if there are a lot of subdirectories.

The owner value only changes when you switch from regular mode to secure mode 
and vice-versa.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-17937) Ambari install/init should create a new gpadmin database

[Lav Jain (JIRA)]

Lav Jain created AMBARI-17937:
-

 Summary: Ambari install/init should create a new gpadmin database
 Key: AMBARI-17937
 URL: https://issues.apache.org/jira/browse/AMBARI-17937
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Lav Jain
Assignee: Lav Jain
Priority: Minor
 Fix For: 2.4.0


If you are logged in as gpadmin on the master and type in "psql" to connect to 
the database, it will fail.  psql assumes you want to connect to the database 
named "gpadmin" which matches your username. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17717) Ambari should have a script to add new repository and service to existing stack

[Lav Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-17717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15384801#comment-15384801
 ] 

Lav Jain commented on AMBARI-17717:
---

Hi [~jluniya] Could you please elaborate on why this patch doesn't meet the bar 
for Ambari 2.4.0?

The goal for the script was for wider adoption of Apache HAWQ as well as Ambari 
(giving end users the capability to deploy open source software through Ambari).

The script generic enough to deploy any service that resides under 
common-services. We can also enhance this script to include services under 
stack extentions.

> Ambari should have a script to add new repository and service to existing 
> stack
> ---
>
> Key: AMBARI-17717
> URL: https://issues.apache.org/jira/browse/AMBARI-17717
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-17717.patch
>
>
> Ambari should have a script that users can run to add a custom service and 
> repository to the stack or an existing cluster.
> {code}
> Lavs-MacBook-Pro:scripts ljain$ ./add_common_service.py -h
> Usage: add_common_service.py [options]
> Options:
>   -h, --helpshow this help message and exit
>   -u USER, --user=USER  Ambari login username (Required)
>   -p PASSWORD, --password=PASSWORD
> Ambari login password. Providing password through
> command line is not recommended. The script prompts
> for the password.
>   -t STACK, --stack=STACK
> Stack Name and Version to be added (Required).(Eg:
> HDP-2.4 or HDP-2.5)
>   -s SERVICE, --service=SERVICE
> Service Name and Version to be added.(Eg: HAWQ/2.0.0
> or PXF/3.0.0)
>   -r REPOURL, --repourl=REPOURL
> Repository URL which points to the rpm packages
>   -i REPOID, --repoid=REPOID
> Repository ID of the new repository
>   -o OSTYPE, --ostype=OSTYPE
> OS for the new repository (Eg: redhat6)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17717) Ambari should have a script to add new repository and service to existing stack

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-17717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-17717:
--
Status: Patch Available  (was: Open)

> Ambari should have a script to add new repository and service to existing 
> stack
> ---
>
> Key: AMBARI-17717
> URL: https://issues.apache.org/jira/browse/AMBARI-17717
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-17717.patch
>
>
> Ambari should have a script that users can run to add a custom service and 
> repository to the stack or an existing cluster.
> {code}
> Lavs-MacBook-Pro:scripts ljain$ ./add_common_service.py -h
> Usage: add_common_service.py [options]
> Options:
>   -h, --helpshow this help message and exit
>   -u USER, --user=USER  Ambari login username (Required)
>   -p PASSWORD, --password=PASSWORD
> Ambari login password. Providing password through
> command line is not recommended. The script prompts
> for the password.
>   -t STACK, --stack=STACK
> Stack Name and Version to be added (Required).(Eg:
> HDP-2.4 or HDP-2.5)
>   -s SERVICE, --service=SERVICE
> Service Name and Version to be added.(Eg: HAWQ/2.0.0
> or PXF/3.0.0)
>   -r REPOURL, --repourl=REPOURL
> Repository URL which points to the rpm packages
>   -i REPOID, --repoid=REPOID
> Repository ID of the new repository
>   -o OSTYPE, --ostype=OSTYPE
> OS for the new repository (Eg: redhat6)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17717) Ambari should have a script to add new repository and service to existing stack

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-17717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-17717:
--
Attachment: AMBARI-17717.patch

> Ambari should have a script to add new repository and service to existing 
> stack
> ---
>
> Key: AMBARI-17717
> URL: https://issues.apache.org/jira/browse/AMBARI-17717
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-17717.patch
>
>
> Ambari should have a script that users can run to add a custom service and 
> repository to the stack or an existing cluster.
> {code}
> Lavs-MacBook-Pro:scripts ljain$ ./add_common_service.py -h
> Usage: add_common_service.py [options]
> Options:
>   -h, --helpshow this help message and exit
>   -u USER, --user=USER  Ambari login username (Required)
>   -p PASSWORD, --password=PASSWORD
> Ambari login password. Providing password through
> command line is not recommended. The script prompts
> for the password.
>   -t STACK, --stack=STACK
> Stack Name and Version to be added (Required).(Eg:
> HDP-2.4 or HDP-2.5)
>   -s SERVICE, --service=SERVICE
> Service Name and Version to be added.(Eg: HAWQ/2.0.0
> or PXF/3.0.0)
>   -r REPOURL, --repourl=REPOURL
> Repository URL which points to the rpm packages
>   -i REPOID, --repoid=REPOID
> Repository ID of the new repository
>   -o OSTYPE, --ostype=OSTYPE
> OS for the new repository (Eg: redhat6)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17717) Ambari should have a script to add new repository and service to existing stack

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-17717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-17717:
--
Description: 
Ambari should have a script that users can run to add a custom service and 
repository to the stack or an existing cluster.

{code}
Lavs-MacBook-Pro:scripts ljain$ ./add_common_service.py -h
Usage: add_common_service.py [options]

Options:
  -h, --helpshow this help message and exit
  -u USER, --user=USER  Ambari login username (Required)
  -p PASSWORD, --password=PASSWORD
Ambari login password. Providing password through
command line is not recommended. The script prompts
for the password.
  -t STACK, --stack=STACK
Stack Name and Version to be added (Required).(Eg:
HDP-2.4 or HDP-2.5)
  -s SERVICE, --service=SERVICE
Service Name and Version to be added.(Eg: HAWQ/2.0.0
or PXF/3.0.0)
  -r REPOURL, --repourl=REPOURL
Repository URL which points to the rpm packages
  -i REPOID, --repoid=REPOID
Repository ID of the new repository
  -o OSTYPE, --ostype=OSTYPE
OS for the new repository (Eg: redhat6)
{code}

  was:
Ambari should have a script that users can run to add a custom service and 
repository to the stack or an existing cluster.

Lavs-MacBook-Pro:scripts ljain$ ./add_common_service.py -h
Usage: add_common_service.py [options]

Options:
  -h, --helpshow this help message and exit
  -u USER, --user=USER  Ambari login username (Required)
  -p PASSWORD, --password=PASSWORD
Ambari login password. Providing password through
command line is not recommended. The script prompts
for the password.
  -t STACK, --stack=STACK
Stack Name and Version to be added (Required).(Eg:
HDP-2.4 or HDP-2.5)
  -s SERVICE, --service=SERVICE
Service Name and Version to be added.(Eg: HAWQ/2.0.0
or PXF/3.0.0)
  -r REPOURL, --repourl=REPOURL
Repository URL which points to the rpm packages
  -i REPOID, --repoid=REPOID
Repository ID of the new repository
  -o OSTYPE, --ostype=OSTYPE
OS for the new repository (Eg: redhat6)


> Ambari should have a script to add new repository and service to existing 
> stack
> ---
>
> Key: AMBARI-17717
> URL: https://issues.apache.org/jira/browse/AMBARI-17717
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
>
> Ambari should have a script that users can run to add a custom service and 
> repository to the stack or an existing cluster.
> {code}
> Lavs-MacBook-Pro:scripts ljain$ ./add_common_service.py -h
> Usage: add_common_service.py [options]
> Options:
>   -h, --helpshow this help message and exit
>   -u USER, --user=USER  Ambari login username (Required)
>   -p PASSWORD, --password=PASSWORD
> Ambari login password. Providing password through
> command line is not recommended. The script prompts
> for the password.
>   -t STACK, --stack=STACK
> Stack Name and Version to be added (Required).(Eg:
> HDP-2.4 or HDP-2.5)
>   -s SERVICE, --service=SERVICE
> Service Name and Version to be added.(Eg: HAWQ/2.0.0
> or PXF/3.0.0)
>   -r REPOURL, --repourl=REPOURL
> Repository URL which points to the rpm packages
>   -i REPOID, --repoid=REPOID
> Repository ID of the new repository
>   -o OSTYPE, --ostype=OSTYPE
> OS for the new repository (Eg: redhat6)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17717) Ambari should have a script to add new repository and service to existing stack

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-17717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-17717:
--
Description: 
Ambari should have a script that users can run to add a custom service and 
repository to the stack or an existing cluster.

Lavs-MacBook-Pro:scripts ljain$ ./add_common_service.py -h
Usage: add_common_service.py [options]

Options:
  -h, --helpshow this help message and exit
  -u USER, --user=USER  Ambari login username (Required)
  -p PASSWORD, --password=PASSWORD
Ambari login password. Providing password through
command line is not recommended. The script prompts
for the password.
  -t STACK, --stack=STACK
Stack Name and Version to be added (Required).(Eg:
HDP-2.4 or HDP-2.5)
  -s SERVICE, --service=SERVICE
Service Name and Version to be added.(Eg: HAWQ/2.0.0
or PXF/3.0.0)
  -r REPOURL, --repourl=REPOURL
Repository URL which points to the rpm packages
  -i REPOID, --repoid=REPOID
Repository ID of the new repository
  -o OSTYPE, --ostype=OSTYPE
OS for the new repository (Eg: redhat6)

  was:Ambari should have a script that users can run to add a custom service 
and repository to the stack or an existing cluster.


> Ambari should have a script to add new repository and service to existing 
> stack
> ---
>
> Key: AMBARI-17717
> URL: https://issues.apache.org/jira/browse/AMBARI-17717
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
>
> Ambari should have a script that users can run to add a custom service and 
> repository to the stack or an existing cluster.
> Lavs-MacBook-Pro:scripts ljain$ ./add_common_service.py -h
> Usage: add_common_service.py [options]
> Options:
>   -h, --helpshow this help message and exit
>   -u USER, --user=USER  Ambari login username (Required)
>   -p PASSWORD, --password=PASSWORD
> Ambari login password. Providing password through
> command line is not recommended. The script prompts
> for the password.
>   -t STACK, --stack=STACK
> Stack Name and Version to be added (Required).(Eg:
> HDP-2.4 or HDP-2.5)
>   -s SERVICE, --service=SERVICE
> Service Name and Version to be added.(Eg: HAWQ/2.0.0
> or PXF/3.0.0)
>   -r REPOURL, --repourl=REPOURL
> Repository URL which points to the rpm packages
>   -i REPOID, --repoid=REPOID
> Repository ID of the new repository
>   -o OSTYPE, --ostype=OSTYPE
> OS for the new repository (Eg: redhat6)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17700) Slider range for should be dynamic on HAWQ settings page

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-17700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-17700:
--
Status: Patch Available  (was: Open)

> Slider range for should be dynamic on HAWQ settings page
> 
>
> Key: AMBARI-17700
> URL: https://issues.apache.org/jira/browse/AMBARI-17700
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-17700.branch24.patch
>
>
> Ambari should dynamically update the slider range on HAWQ parameters on 
> settings page depending on the cluster size because the static range isn't 
> usable and does not allow selecting a smaller desired value. E.g. the maximum 
> value of 1 is too large when setting it to less than 10.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-17700) Slider range for should be dynamic on HAWQ settings page

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-17700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-17700:
--
Attachment: AMBARI-17700.branch24.patch

> Slider range for should be dynamic on HAWQ settings page
> 
>
> Key: AMBARI-17700
> URL: https://issues.apache.org/jira/browse/AMBARI-17700
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-17700.branch24.patch
>
>
> Ambari should dynamically update the slider range on HAWQ parameters on 
> settings page depending on the cluster size because the static range isn't 
> usable and does not allow selecting a smaller desired value. E.g. the maximum 
> value of 1 is too large when setting it to less than 10.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-17700) Slider range for should be dynamic on HAWQ settings page

[Lav Jain (JIRA)]

Lav Jain created AMBARI-17700:
-

 Summary: Slider range for should be dynamic on HAWQ settings page
 Key: AMBARI-17700
 URL: https://issues.apache.org/jira/browse/AMBARI-17700
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: trunk, 2.4.0
Reporter: Lav Jain
Assignee: Lav Jain
 Fix For: trunk, 2.4.0


Ambari should dynamically update the slider range on HAWQ parameters on 
settings page depending on the cluster size because the static range isn't 
usable and does not allow selecting a smaller desired value. E.g. the maximum 
value of 1 is too large when setting it to less than 10.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-17700) Slider range for should be dynamic on HAWQ settings page

[Lav Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-17700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376033#comment-15376033
 ] 

Lav Jain commented on AMBARI-17700:
---

A patch for this issue should be available later this week.

> Slider range for should be dynamic on HAWQ settings page
> 
>
> Key: AMBARI-17700
> URL: https://issues.apache.org/jira/browse/AMBARI-17700
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: trunk, 2.4.0
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
>
> Ambari should dynamically update the slider range on HAWQ parameters on 
> settings page depending on the cluster size because the static range isn't 
> usable and does not allow selecting a smaller desired value. E.g. the maximum 
> value of 1 is too large when setting it to less than 10.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16665) Cache service advisors when stack advisor is loaded

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16665:
--
   Resolution: Fixed
Fix Version/s: trunk
   Status: Resolved  (was: Patch Available)

[~jluniya]
It was already checked into trunk and 2.4, but missed changing the status to 
resolved.

> Cache service advisors when stack advisor is loaded
> ---
>
> Key: AMBARI-16665
> URL: https://issues.apache.org/jira/browse/AMBARI-16665
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16665.branch24.patch, 
> AMBARI-16665.branch24.v2.patch, AMBARI-16665.patch, AMBARI-16665.v2.patch
>
>
> With the current implementation, service advisors for the same service are 
> loaded multiple times in the stack advisor.
> The service advisors should be cached when the stack advisor is loaded and 
> used where necessary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16665) Cache service advisors when stack advisor is loaded

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16665:
--
Fix Version/s: (was: 2.5.0)
   2.4.0

> Cache service advisors when stack advisor is loaded
> ---
>
> Key: AMBARI-16665
> URL: https://issues.apache.org/jira/browse/AMBARI-16665
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: 2.4.0
>
> Attachments: AMBARI-16665.branch24.patch, 
> AMBARI-16665.branch24.v2.patch, AMBARI-16665.patch, AMBARI-16665.v2.patch
>
>
> With the current implementation, service advisors for the same service are 
> loaded multiple times in the stack advisor.
> The service advisors should be cached when the stack advisor is loaded and 
> used where necessary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16647) Move service advisor tests for HAWQ and PXF

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16647:
--
Status: Patch Available  (was: In Progress)

> Move service advisor tests for HAWQ and PXF
> ---
>
> Key: AMBARI-16647
> URL: https://issues.apache.org/jira/browse/AMBARI-16647
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
>Priority: Minor
> Fix For: trunk, 2.4.1
>
> Attachments: AMBARI-16647.patch, AMBARI-16647.v2.patch, 
> AMBARI-16647.v3.patch
>
>
> Currently the service advisor tests for HAWQ and PXF are under 
> ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py
> Move the tests to the service specific service_advisor files:
> ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py
> ambari-server/src/test/python/common-services/PXF/test_service_advisor.py



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16647) Move service advisor tests for HAWQ and PXF

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16647:
--
Status: In Progress  (was: Patch Available)

> Move service advisor tests for HAWQ and PXF
> ---
>
> Key: AMBARI-16647
> URL: https://issues.apache.org/jira/browse/AMBARI-16647
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
>Priority: Minor
> Fix For: trunk, 2.4.1
>
> Attachments: AMBARI-16647.patch, AMBARI-16647.v2.patch, 
> AMBARI-16647.v3.patch
>
>
> Currently the service advisor tests for HAWQ and PXF are under 
> ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py
> Move the tests to the service specific service_advisor files:
> ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py
> ambari-server/src/test/python/common-services/PXF/test_service_advisor.py



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16647) Move service advisor tests for HAWQ and PXF

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16647:
--
Attachment: AMBARI-16647.v3.patch

> Move service advisor tests for HAWQ and PXF
> ---
>
> Key: AMBARI-16647
> URL: https://issues.apache.org/jira/browse/AMBARI-16647
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
>Priority: Minor
> Fix For: trunk, 2.4.1
>
> Attachments: AMBARI-16647.patch, AMBARI-16647.v2.patch, 
> AMBARI-16647.v3.patch
>
>
> Currently the service advisor tests for HAWQ and PXF are under 
> ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py
> Move the tests to the service specific service_advisor files:
> ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py
> ambari-server/src/test/python/common-services/PXF/test_service_advisor.py



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (AMBARI-16780) Move service advisor HAWQ and PXF tests from 2.3 and common stack_advisor folder to common-services folder

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain reassigned AMBARI-16780:
-

Assignee: Lav Jain

> Move service advisor HAWQ and PXF tests from 2.3 and common stack_advisor 
> folder to common-services folder
> --
>
> Key: AMBARI-16780
> URL: https://issues.apache.org/jira/browse/AMBARI-16780
> Project: Ambari
>  Issue Type: Sub-task
>  Components: stacks
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (AMBARI-16758) Revisit HAWQ and PXF unit tests and refactor code

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain reassigned AMBARI-16758:
-

Assignee: Lav Jain

> Revisit HAWQ and PXF unit tests and refactor code
> -
>
> Key: AMBARI-16758
> URL: https://issues.apache.org/jira/browse/AMBARI-16758
> Project: Ambari
>  Issue Type: Technical task
>  Components: stacks
>Reporter: Matt
>Assignee: Lav Jain
>Priority: Minor
> Fix For: trunk
>
>
> Refactor HAWQ and PXF unit tests
> [~lavjain] notes: 
> {code}
> ExecuteScript can be a separate function with command passed in as parameter.
> Similarily, common.stop_component can be refactored into a separate function 
> with both test_stop_default and test_activate_hawq_standby calling it.
> If you want to go one step further, create a base class of 
> TestHawqCommon(RMFTestCase) that defines the corresponding routines in 
> common.py with TestHawqStandby(TestHawqCommon).
> assertResourceCalled can be defined using functools.partial
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16647) Move service advisor tests for HAWQ and PXF

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16647:
--
Status: In Progress  (was: Patch Available)

> Move service advisor tests for HAWQ and PXF
> ---
>
> Key: AMBARI-16647
> URL: https://issues.apache.org/jira/browse/AMBARI-16647
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
>Priority: Minor
> Fix For: trunk, 2.4.1
>
> Attachments: AMBARI-16647.patch, AMBARI-16647.v2.patch
>
>
> Currently the service advisor tests for HAWQ and PXF are under 
> ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py
> Move the tests to the service specific service_advisor files:
> ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py
> ambari-server/src/test/python/common-services/PXF/test_service_advisor.py



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16647) Move service advisor tests for HAWQ and PXF

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16647:
--
Attachment: AMBARI-16647.v2.patch

> Move service advisor tests for HAWQ and PXF
> ---
>
> Key: AMBARI-16647
> URL: https://issues.apache.org/jira/browse/AMBARI-16647
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
>Priority: Minor
> Fix For: trunk, 2.4.1
>
> Attachments: AMBARI-16647.patch, AMBARI-16647.v2.patch
>
>
> Currently the service advisor tests for HAWQ and PXF are under 
> ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py
> Move the tests to the service specific service_advisor files:
> ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py
> ambari-server/src/test/python/common-services/PXF/test_service_advisor.py



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16647) Move service advisor tests for HAWQ and PXF

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16647:
--
Status: Patch Available  (was: In Progress)

> Move service advisor tests for HAWQ and PXF
> ---
>
> Key: AMBARI-16647
> URL: https://issues.apache.org/jira/browse/AMBARI-16647
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
>Priority: Minor
> Fix For: trunk, 2.4.1
>
> Attachments: AMBARI-16647.patch, AMBARI-16647.v2.patch
>
>
> Currently the service advisor tests for HAWQ and PXF are under 
> ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py
> Move the tests to the service specific service_advisor files:
> ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py
> ambari-server/src/test/python/common-services/PXF/test_service_advisor.py



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16647) Move service advisor tests for HAWQ and PXF

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16647:
--
Fix Version/s: 2.4.1
Affects Version/s: 2.4.0
   trunk
   Status: Patch Available  (was: Open)

> Move service advisor tests for HAWQ and PXF
> ---
>
> Key: AMBARI-16647
> URL: https://issues.apache.org/jira/browse/AMBARI-16647
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
>Priority: Minor
> Fix For: trunk, 2.4.1
>
> Attachments: AMBARI-16647.patch
>
>
> Currently the service advisor tests for HAWQ and PXF are under 
> ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py
> Move the tests to the service specific service_advisor files:
> ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py
> ambari-server/src/test/python/common-services/PXF/test_service_advisor.py



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16647) Move service advisor tests for HAWQ and PXF

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16647:
--
Attachment: AMBARI-16647.patch

> Move service advisor tests for HAWQ and PXF
> ---
>
> Key: AMBARI-16647
> URL: https://issues.apache.org/jira/browse/AMBARI-16647
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Reporter: Matt
>Assignee: Lav Jain
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-16647.patch
>
>
> Currently the service advisor tests for HAWQ and PXF are under 
> ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py
> Move the tests to the service specific service_advisor files:
> ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py
> ambari-server/src/test/python/common-services/PXF/test_service_advisor.py



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (AMBARI-16647) Move service advisor tests for HAWQ and PXF

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain reassigned AMBARI-16647:
-

Assignee: Lav Jain

> Move service advisor tests for HAWQ and PXF
> ---
>
> Key: AMBARI-16647
> URL: https://issues.apache.org/jira/browse/AMBARI-16647
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Reporter: Matt
>Assignee: Lav Jain
>Priority: Minor
> Fix For: trunk
>
>
> Currently the service advisor tests for HAWQ and PXF are under 
> ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py
> Move the tests to the service specific service_advisor files:
> ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py
> ambari-server/src/test/python/common-services/PXF/test_service_advisor.py



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15317722#comment-15317722
 ] 

Lav Jain commented on AMBARI-16663:
---

Rebased to trunk code

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, 
> AMBARI-16663.branch24.v2.patch, AMBARI-16663.branch24.v3.patch, 
> AMBARI-16663.branch24.v4.patch, AMBARI-16663.patch, AMBARI-16663.v2.patch, 
> AMBARI-16663.v3.patch, AMBARI-16663.v4.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16663:
--
Status: Patch Available  (was: In Progress)

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, 
> AMBARI-16663.branch24.v2.patch, AMBARI-16663.branch24.v3.patch, 
> AMBARI-16663.branch24.v4.patch, AMBARI-16663.patch, AMBARI-16663.v2.patch, 
> AMBARI-16663.v3.patch, AMBARI-16663.v4.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16663:
--
Status: In Progress  (was: Patch Available)

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, 
> AMBARI-16663.branch24.v2.patch, AMBARI-16663.branch24.v3.patch, 
> AMBARI-16663.branch24.v4.patch, AMBARI-16663.patch, AMBARI-16663.v2.patch, 
> AMBARI-16663.v3.patch, AMBARI-16663.v4.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16663:
--
Attachment: AMBARI-16663.v4.patch

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, 
> AMBARI-16663.branch24.v2.patch, AMBARI-16663.branch24.v3.patch, 
> AMBARI-16663.branch24.v4.patch, AMBARI-16663.patch, AMBARI-16663.v2.patch, 
> AMBARI-16663.v3.patch, AMBARI-16663.v4.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16663:
--
Attachment: AMBARI-16663.branch24.v4.patch

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, 
> AMBARI-16663.branch24.v2.patch, AMBARI-16663.branch24.v3.patch, 
> AMBARI-16663.branch24.v4.patch, AMBARI-16663.patch, AMBARI-16663.v2.patch, 
> AMBARI-16663.v3.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16663:
--
Status: In Progress  (was: Patch Available)

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, 
> AMBARI-16663.branch24.v2.patch, AMBARI-16663.branch24.v3.patch, 
> AMBARI-16663.patch, AMBARI-16663.v2.patch, AMBARI-16663.v3.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16663:
--
Attachment: AMBARI-16663.v3.patch

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, 
> AMBARI-16663.branch24.v2.patch, AMBARI-16663.branch24.v3.patch, 
> AMBARI-16663.patch, AMBARI-16663.v2.patch, AMBARI-16663.v3.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16663:
--
Status: Patch Available  (was: In Progress)

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, 
> AMBARI-16663.branch24.v2.patch, AMBARI-16663.branch24.v3.patch, 
> AMBARI-16663.patch, AMBARI-16663.v2.patch, AMBARI-16663.v3.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16663:
--
Attachment: AMBARI-16663.v2.patch

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, 
> AMBARI-16663.branch24.v2.patch, AMBARI-16663.patch, AMBARI-16663.v2.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15316051#comment-15316051
 ] 

Lav Jain commented on AMBARI-16663:
---

Patch update to fix the test failures.

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, 
> AMBARI-16663.branch24.v2.patch, AMBARI-16663.patch, AMBARI-16663.v2.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16663:
--
Status: Patch Available  (was: In Progress)

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, 
> AMBARI-16663.branch24.v2.patch, AMBARI-16663.patch, AMBARI-16663.v2.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16663:
--
Status: In Progress  (was: Patch Available)

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, 
> AMBARI-16663.branch24.v2.patch, AMBARI-16663.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16663:
--
Attachment: AMBARI-16663.branch24.v2.patch

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, 
> AMBARI-16663.branch24.v2.patch, AMBARI-16663.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16663:
--
Fix Version/s: 2.4.0
   trunk
   Status: Patch Available  (was: Open)

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16663.branch24.patch, AMBARI-16663.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16663:
--
Attachment: AMBARI-16663.patch

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Attachments: AMBARI-16663.branch24.patch, AMBARI-16663.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16663:
--
Attachment: AMBARI-16663.branch24.patch

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Attachments: AMBARI-16663.branch24.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16663:
--
Summary: Refactor service_advisor apis to remove passing of stack_advisor  
(was: Move utilities common to stack and service advisors to a separate 
advisor_utils class)

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16663) Move utilities common to stack and service advisors to a separate advisor_utils class

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16663:
--
 Assignee: Lav Jain
Affects Version/s: 2.4.0
   trunk
 Priority: Major  (was: Minor)
  Component/s: (was: stacks)
   ambari-server
   Issue Type: Improvement  (was: Bug)
  Summary: Move utilities common to stack and service advisors to a 
separate advisor_utils class  (was: Refactor service_advisor apis to remove 
passing of stack_advisor)

> Move utilities common to stack and service advisors to a separate 
> advisor_utils class
> -
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16663) Refactor service_advisor apis to remove passing of stack_advisor

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16663:
--
Summary: Refactor service_advisor apis to remove passing of stack_advisor  
(was: Move utilities common to stack and service advisors to a separate 
advisor_utils class)

> Refactor service_advisor apis to remove passing of stack_advisor
> 
>
> Key: AMBARI-16663
> URL: https://issues.apache.org/jira/browse/AMBARI-16663
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Reporter: Matt
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-16665) Cache service advisors when stack advisor is loaded

[Lav Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-16665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304591#comment-15304591
 ] 

Lav Jain commented on AMBARI-16665:
---

Rebased with trunk.

> Cache service advisors when stack advisor is loaded
> ---
>
> Key: AMBARI-16665
> URL: https://issues.apache.org/jira/browse/AMBARI-16665
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16665.branch24.patch, 
> AMBARI-16665.branch24.v2.patch, AMBARI-16665.patch, AMBARI-16665.v2.patch
>
>
> With the current implementation, service advisors for the same service are 
> loaded multiple times in the stack advisor.
> The service advisors should be cached when the stack advisor is loaded and 
> used where necessary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16665) Cache service advisors when stack advisor is loaded

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16665:
--
Status: Patch Available  (was: In Progress)

> Cache service advisors when stack advisor is loaded
> ---
>
> Key: AMBARI-16665
> URL: https://issues.apache.org/jira/browse/AMBARI-16665
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16665.branch24.patch, 
> AMBARI-16665.branch24.v2.patch, AMBARI-16665.patch, AMBARI-16665.v2.patch
>
>
> With the current implementation, service advisors for the same service are 
> loaded multiple times in the stack advisor.
> The service advisors should be cached when the stack advisor is loaded and 
> used where necessary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16665) Cache service advisors when stack advisor is loaded

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16665:
--
Status: In Progress  (was: Patch Available)

> Cache service advisors when stack advisor is loaded
> ---
>
> Key: AMBARI-16665
> URL: https://issues.apache.org/jira/browse/AMBARI-16665
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16665.branch24.patch, 
> AMBARI-16665.branch24.v2.patch, AMBARI-16665.patch, AMBARI-16665.v2.patch
>
>
> With the current implementation, service advisors for the same service are 
> loaded multiple times in the stack advisor.
> The service advisors should be cached when the stack advisor is loaded and 
> used where necessary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16665) Cache service advisors when stack advisor is loaded

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16665:
--
Attachment: AMBARI-16665.v2.patch

> Cache service advisors when stack advisor is loaded
> ---
>
> Key: AMBARI-16665
> URL: https://issues.apache.org/jira/browse/AMBARI-16665
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16665.branch24.patch, 
> AMBARI-16665.branch24.v2.patch, AMBARI-16665.patch, AMBARI-16665.v2.patch
>
>
> With the current implementation, service advisors for the same service are 
> loaded multiple times in the stack advisor.
> The service advisors should be cached when the stack advisor is loaded and 
> used where necessary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16665) Cache service advisors when stack advisor is loaded

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16665:
--
Attachment: AMBARI-16665.branch24.v2.patch

> Cache service advisors when stack advisor is loaded
> ---
>
> Key: AMBARI-16665
> URL: https://issues.apache.org/jira/browse/AMBARI-16665
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16665.branch24.patch, 
> AMBARI-16665.branch24.v2.patch, AMBARI-16665.patch
>
>
> With the current implementation, service advisors for the same service are 
> loaded multiple times in the stack advisor.
> The service advisors should be cached when the stack advisor is loaded and 
> used where necessary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16665) Cache service advisors when stack advisor is loaded

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16665:
--
Status: Patch Available  (was: Open)

> Cache service advisors when stack advisor is loaded
> ---
>
> Key: AMBARI-16665
> URL: https://issues.apache.org/jira/browse/AMBARI-16665
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16665.branch24.patch, AMBARI-16665.patch
>
>
> With the current implementation, service advisors for the same service are 
> loaded multiple times in the stack advisor.
> The service advisors should be cached when the stack advisor is loaded and 
> used where necessary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16665) Cache service advisors when stack advisor is loaded

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16665:
--
Affects Version/s: 2.4.0
   trunk
 Priority: Major  (was: Minor)
Fix Version/s: 2.4.0
   trunk

> Cache service advisors when stack advisor is loaded
> ---
>
> Key: AMBARI-16665
> URL: https://issues.apache.org/jira/browse/AMBARI-16665
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16665.branch24.patch, AMBARI-16665.patch
>
>
> With the current implementation, service advisors for the same service are 
> loaded multiple times in the stack advisor.
> The service advisors should be cached when the stack advisor is loaded and 
> used where necessary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16665) Cache service advisors when stack advisor is loaded

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16665:
--
Attachment: AMBARI-16665.patch

> Cache service advisors when stack advisor is loaded
> ---
>
> Key: AMBARI-16665
> URL: https://issues.apache.org/jira/browse/AMBARI-16665
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16665.branch24.patch, AMBARI-16665.patch
>
>
> With the current implementation, service advisors for the same service are 
> loaded multiple times in the stack advisor.
> The service advisors should be cached when the stack advisor is loaded and 
> used where necessary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16665) Cache service advisors when stack advisor is loaded

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16665:
--
Attachment: AMBARI-16665.branch24.patch

> Cache service advisors when stack advisor is loaded
> ---
>
> Key: AMBARI-16665
> URL: https://issues.apache.org/jira/browse/AMBARI-16665
> Project: Ambari
>  Issue Type: Improvement
>  Components: stacks
>Reporter: Matt
>Assignee: Lav Jain
>Priority: Minor
> Attachments: AMBARI-16665.branch24.patch
>
>
> With the current implementation, service advisors for the same service are 
> loaded multiple times in the stack advisor.
> The service advisors should be cached when the stack advisor is loaded and 
> used where necessary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-16378) stackadvisor uses getHostsForSlaveComponent with wrong parameter name

[Lav Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-16378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15278607#comment-15278607
 ] 

Lav Jain commented on AMBARI-16378:
---

Excellent [~sumitmohanty]. Thanks for the commit!

> stackadvisor uses getHostsForSlaveComponent with wrong parameter name
> -
>
> Key: AMBARI-16378
> URL: https://issues.apache.org/jira/browse/AMBARI-16378
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: trunk
>
> Attachments: AMBARI-16378.patch
>
>
> {code}
>   def getHostsForSlaveComponent(self, services, hosts, component, hostsList, 
> hostsComponentsMap, freeHosts):
> componentName = component["StackServiceComponents"]["component_name"]
> if component["StackServiceComponents"]["cardinality"] == "ALL":
>   return hostsList
> componentIsPopulated = self.isComponentHostsPopulated(component)
> if componentIsPopulated:
>   return component["StackServiceComponents"]["hostnames"]
> hostsForComponent = []
> if self.isSlaveComponent(component):
>   cardinality = str(component["StackServiceComponents"]["cardinality"])
>   if self.isComponentUsingCardinalityForLayout(component) and cardinality:
> # cardinality types: 1+, 1-2, 1
> {code}
> The correct parameter name is comonentName (instead of component)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16378) stackadvisor uses getHostsForSlaveComponent with wrong parameter name

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16378:
--
Attachment: AMBARI-16378.patch

> stackadvisor uses getHostsForSlaveComponent with wrong parameter name
> -
>
> Key: AMBARI-16378
> URL: https://issues.apache.org/jira/browse/AMBARI-16378
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: trunk
>
> Attachments: AMBARI-16378.patch
>
>
> {code}
>   def getHostsForSlaveComponent(self, services, hosts, component, hostsList, 
> hostsComponentsMap, freeHosts):
> componentName = component["StackServiceComponents"]["component_name"]
> if component["StackServiceComponents"]["cardinality"] == "ALL":
>   return hostsList
> componentIsPopulated = self.isComponentHostsPopulated(component)
> if componentIsPopulated:
>   return component["StackServiceComponents"]["hostnames"]
> hostsForComponent = []
> if self.isSlaveComponent(component):
>   cardinality = str(component["StackServiceComponents"]["cardinality"])
>   if self.isComponentUsingCardinalityForLayout(component) and cardinality:
> # cardinality types: 1+, 1-2, 1
> {code}
> The correct parameter name is comonentName (instead of component)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (AMBARI-16378) stackadvisor uses getHostsForSlaveComponent with wrong parameter name

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain reassigned AMBARI-16378:
-

Assignee: Lav Jain

> stackadvisor uses getHostsForSlaveComponent with wrong parameter name
> -
>
> Key: AMBARI-16378
> URL: https://issues.apache.org/jira/browse/AMBARI-16378
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: trunk
>
>
> {code}
>   def getHostsForSlaveComponent(self, services, hosts, component, hostsList, 
> hostsComponentsMap, freeHosts):
> componentName = component["StackServiceComponents"]["component_name"]
> if component["StackServiceComponents"]["cardinality"] == "ALL":
>   return hostsList
> componentIsPopulated = self.isComponentHostsPopulated(component)
> if componentIsPopulated:
>   return component["StackServiceComponents"]["hostnames"]
> hostsForComponent = []
> if self.isSlaveComponent(component):
>   cardinality = str(component["StackServiceComponents"]["cardinality"])
>   if self.isComponentUsingCardinalityForLayout(component) and cardinality:
> # cardinality types: 1+, 1-2, 1
> {code}
> The correct parameter name is comonentName (instead of component)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-16378) stackadvisor uses getHostsForSlaveComponent with wrong parameter name

[Lav Jain (JIRA)]

Lav Jain created AMBARI-16378:
-

 Summary: stackadvisor uses getHostsForSlaveComponent with wrong 
parameter name
 Key: AMBARI-16378
 URL: https://issues.apache.org/jira/browse/AMBARI-16378
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: trunk
Reporter: Lav Jain
 Fix For: trunk


{code}
  def getHostsForSlaveComponent(self, services, hosts, component, hostsList, 
hostsComponentsMap, freeHosts):
componentName = component["StackServiceComponents"]["component_name"]

if component["StackServiceComponents"]["cardinality"] == "ALL":
  return hostsList

componentIsPopulated = self.isComponentHostsPopulated(component)
if componentIsPopulated:
  return component["StackServiceComponents"]["hostnames"]

hostsForComponent = []

if self.isSlaveComponent(component):
  cardinality = str(component["StackServiceComponents"]["cardinality"])
  if self.isComponentUsingCardinalityForLayout(component) and cardinality:
# cardinality types: 1+, 1-2, 1
{code}

The correct parameter name is comonentName (instead of component)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (AMBARI-16192) 'Restart All' for HAWQ should follow role_command_order

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain reopened AMBARI-16192:
---

Closed by mistake (yet to commit).

> 'Restart All' for HAWQ should follow role_command_order
> ---
>
> Key: AMBARI-16192
> URL: https://issues.apache.org/jira/browse/AMBARI-16192
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: trunk, 2.2.2
>Reporter: Lav Jain
>Assignee: Lav Jain
>Priority: Minor
> Fix For: 2.4.0, 2.2-next
>
> Attachments: AMBARI-16192.branch22.patch, AMBARI-16192.patch
>
>
> The current implementation in Ambari, 'Restart All' service action does not 
> follow role_command_order.
> For example, all HAWQSEGMENTs start before HAWQMASTER and HAWQSTANDBY starts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16192) 'Restart All' for HAWQ should follow role_command_order

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16192:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> 'Restart All' for HAWQ should follow role_command_order
> ---
>
> Key: AMBARI-16192
> URL: https://issues.apache.org/jira/browse/AMBARI-16192
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: trunk, 2.2.2
>Reporter: Lav Jain
>Assignee: Lav Jain
>Priority: Minor
> Fix For: 2.4.0, 2.2-next
>
> Attachments: AMBARI-16192.branch22.patch, AMBARI-16192.patch
>
>
> The current implementation in Ambari, 'Restart All' service action does not 
> follow role_command_order.
> For example, all HAWQSEGMENTs start before HAWQMASTER and HAWQSTANDBY starts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16192) 'Restart All' for HAWQ should follow role_command_order

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16192:
--
Attachment: AMBARI-16192.patch

> 'Restart All' for HAWQ should follow role_command_order
> ---
>
> Key: AMBARI-16192
> URL: https://issues.apache.org/jira/browse/AMBARI-16192
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: trunk, 2.2.2
>Reporter: Lav Jain
>Assignee: Lav Jain
>Priority: Minor
> Attachments: AMBARI-16192.branch22.patch, AMBARI-16192.patch
>
>
> The current implementation in Ambari, 'Restart All' service action does not 
> follow role_command_order.
> For example, all HAWQSEGMENTs start before HAWQMASTER and HAWQSTANDBY starts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-16192) 'Restart All' for HAWQ should follow role_command_order

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-16192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-16192:
--
Attachment: AMBARI-16192.branch22.patch

> 'Restart All' for HAWQ should follow role_command_order
> ---
>
> Key: AMBARI-16192
> URL: https://issues.apache.org/jira/browse/AMBARI-16192
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-web
>Affects Versions: trunk, 2.2.2
>Reporter: Lav Jain
>Assignee: Lav Jain
>Priority: Minor
> Attachments: AMBARI-16192.branch22.patch
>
>
> The current implementation in Ambari, 'Restart All' service action does not 
> follow role_command_order.
> For example, all HAWQSEGMENTs start before HAWQMASTER and HAWQSTANDBY starts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-16192) 'Restart All' for HAWQ should follow role_command_order

[Lav Jain (JIRA)]

Lav Jain created AMBARI-16192:
-

 Summary: 'Restart All' for HAWQ should follow role_command_order
 Key: AMBARI-16192
 URL: https://issues.apache.org/jira/browse/AMBARI-16192
 Project: Ambari
  Issue Type: Improvement
  Components: ambari-web
Affects Versions: trunk, 2.2.2
Reporter: Lav Jain
Assignee: Lav Jain
Priority: Minor


The current implementation in Ambari, 'Restart All' service action does not 
follow role_command_order.

For example, all HAWQSEGMENTs start before HAWQMASTER and HAWQSTANDBY starts.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15657) HAWQ config should not allow multiple Master/Segment directories

[Lav Jain (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15252792#comment-15252792
 ] 

Lav Jain commented on AMBARI-15657:
---

Hi [~aantonenko], Thanks a lot for letting us know.

The rationale was that if some configuration change results in an ERROR, the 
user should not be allowed to proceed. Otherwise, the validation should trigger 
a WARN (instead of ERROR). Currently, there is no distinction between the two.


> HAWQ config should not allow multiple Master/Segment directories
> 
>
> Key: AMBARI-15657
> URL: https://issues.apache.org/jira/browse/AMBARI-15657
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk, 2.2.0
>Reporter: Lav Jain
>Assignee: Lav Jain
>Priority: Minor
> Attachments: AMBARI-15657.branch22.patch, AMBARI-15657.patch, 
> screenshot.png
>
>
> User can add multiple space delimited directories, but after installation, it 
> shows a comma in between. however, only first directory goes into effect, 
> that too with a comma in the end.
> {code}
> [pivotal@ip-10-32-36-213 etc]$ cat hawq-site.xml
> 
>   hawq_master_directory
>   /data/hawq/master,/data/hawq/master2
> 
> 
>   hawq_segment_directory
>   /data/hawq/segment,/data/hawq/segment2
> 
> [pivotal@ip-10-32-36-213 etc]$ ls -l /data/hawq
> drwxr-xr-x 3 root root 4096 Mar 12 01:00 master,
> drwxr-xr-x 3 root root 4096 Mar 12 01:00 segment,
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15954) PXF Check fails on Kerberized cluster without a YARN component

[Lav Jain (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-15954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lav Jain updated AMBARI-15954:
--
Status: Patch Available  (was: In Progress)

> PXF Check fails on Kerberized cluster without a YARN component
> --
>
> Key: AMBARI-15954
> URL: https://issues.apache.org/jira/browse/AMBARI-15954
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk, 2.2.2
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: 2.3.0, 2.2.2
>
> Attachments: AMBARI-15954.branch22.patch, AMBARI-15954.patch
>
>
> If the PXF component is not co-located with a YARN component, PXF service 
> check would fail. This is because it requires yarn-site on that host.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)