Re: hawq Ambari integration

Ranger community advises against sync between Ranger policies and native authorization metastores. It complicates design and users haven't shown a real need to switch between auth models back and forth. -Vineet On Thu, Mar 2, 2017 at 6:33 PM Alexander Denissov wrote: >

Re: hawq Ambari integration

Not quite. For the first phase, there will be no integration between GRANT/REVOKE and Ranger policies -- once Ranger is turned on, GRANT/REVOKE from psql will no longer work. In a later stage, we will likely provide integration HAWQ --> Ranger, such that when GRANT/REVOKE is issued from psql, an

Re: hawq Ambari integration

Have I misunderstood the Ranger integration work? When a GRANT/REVOKE is executed in HAWQ it will be replicated to Ranger and when a GRANT/REVOKE is executed in Ranger, it will be replicated to HAWQ. Right? If yes, then this is the model that I'm suggesting for Ambari. Jon Roberts Principal

Re: hawq Ambari integration

Having worked with Ambari and knowing the complexities of this desired integration, I agree with Alex on his comments below. Users need some time to get used to exclusive HAWQ CLI or Ambari usage model, and avoid mix and match despite the fact that HAWQ CLI and Ambari have their

Re: hawq Ambari integration

Ambari is designed as a tool to sit on top of individual service CLI tools and provide consistent user experience. Ambari can also have wizards and custom actions that go beyond service lifecycle management. It is assumed by Ambari design that once Ambari is used to manage configurations, CLI

[jira] [Created] (HAWQ-1374) RPS still uses policies from 'hawq' serviceName even when name is changed in rps.properties

Alexander Denissov created HAWQ-1374: Summary: RPS still uses policies from 'hawq' serviceName even when name is changed in rps.properties Key: HAWQ-1374 URL: https://issues.apache.org/jira/browse/HAWQ-1374

Re: hawq Ambari integration

Exactly! It would also be easier to communicate steps needed for configuring various GUCs. As of now, we have to alert users in the documentation that they can use the CLI but if they do, they will need to also duplicate the change in Ambari. Jon On Thu, Mar 2, 2017 at 6:39 PM, Lei Chang

Re: New Committer: Kyle Dunn

Congratulations! Kyle. Cheers Lei On Fri, Mar 3, 2017 at 8:30 AM, Kyle Dunn wrote: > Thanks team! Honored to be invited to join this great community! > > > -Kyle > > On Thu, Mar 2, 2017 at 10:07 AM Roman Shaposhnik > wrote: > > > Congrats Kyle! Great

Re: hawq Ambari integration

I think there are some use cases we need What Jon proposed. For example, users installed hawq via Ambari, but they want to automate the configuration changes, it would be convenient to have hawq CLI change the configurations. Cheers Lei On Fri, Mar 3, 2017 at 8:36 AM, Alex (Oleksandr)

Re: hawq Ambari integration

I see, that makes sense. But is there any action users cannot do via Ambari? Ranger is also a good example, there we are making assumption, users either use Ranger or HAWQ's authorization engine. The same logic might be extrapolated to HAWQ/Ambari - users might use either Ambari or HAWQ CLI, but

Re: New Committer: Kyle Dunn

Thanks team! Honored to be invited to join this great community! -Kyle On Thu, Mar 2, 2017 at 10:07 AM Roman Shaposhnik wrote: > Congrats Kyle! Great to have you onboard! > > Thanks, > Roman. > > On Thu, Mar 2, 2017 at 9:05 AM, Ed Espino wrote: > >

Re: hawq Ambari integration

Right. Just like HAWQ will be operational without Ranger. We have the hawq CLI and will obviously continue to have it. Some people use Ambari while others don't. So just like with Ranger support, integrate when possible but don't require it. Jon On Thu, Mar 2, 2017 at 6:26 PM, Alex

Re: hawq Ambari integration

Not really, because HAWQ should be operational even without Ambari(if that's the case). On Thu, Mar 2, 2017 at 4:21 PM, Jon Roberts wrote: > If that is the case, should we remove the "hawq" CLI? > > Jon > > On Thu, Mar 2, 2017 at 6:12 PM, Alex (Oleksandr) Diachenko < >

Re: hawq Ambari integration

If that is the case, should we remove the "hawq" CLI? Jon On Thu, Mar 2, 2017 at 6:12 PM, Alex (Oleksandr) Diachenko < odiache...@pivotal.io> wrote: > Hi Jon, > > I think it was designed that Ambari is supposed to be only one source of > true. > The whole purpose of integration id to provide a

Re: hawq Ambari integration

Hi Jon, I think it was designed that Ambari is supposed to be only one source of true. The whole purpose of integration id to provide a user-friendly interface and avoid manually editing/distributing config files or running CLI commands. The idea of coupling HAWQ master with Ambari doesn't seem

hawq Ambari integration

It would be handy if the "hawq config" also updated Ambari's database so that changes could be made in either place are retained when changes are made in either place. Register Ambari: hawq ambari -u admin -w admin -h myhost -p 8080 "hawq config" could then raise INFO/WARN messages about

[GitHub] incubator-hawq-docs pull request #97: HAWQ-1372 - doc config change without ...

GitHub user lisakowen opened a pull request: https://github.com/apache/incubator-hawq-docs/pull/97 HAWQ-1372 - doc config change without cluster restart for ambari-managed clusters cluster restart for config change in an ambari-managed deployment may not be tolerated in some

[jira] [Created] (HAWQ-1373) command name to reload hawq config (hawq stop cluster -u) is misleading

Lisa Owen created HAWQ-1373: --- Summary: command name to reload hawq config (hawq stop cluster -u) is misleading Key: HAWQ-1373 URL: https://issues.apache.org/jira/browse/HAWQ-1373 Project: Apache HAWQ

Re: New Committer: Kyle Dunn

Congrats Kyle! Great to have you onboard! Thanks, Roman. On Thu, Mar 2, 2017 at 9:05 AM, Ed Espino wrote: > The Project Management Committee (PMC) for Apache HAWQ (incubating) has > invited Kyle Dunn to become a committer and we are pleased to announce that > he has accepted.

New Committer: Kyle Dunn

The Project Management Committee (PMC) for Apache HAWQ (incubating) has invited Kyle Dunn to become a committer and we are pleased to announce that he has accepted. His contributions include (but not limited to): - Issues submitted: He has reported a total of 10 HAWQ issues