hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jon Roberts <jrobe...@pivotal.io>
Subject Re: hawq Ambari integration
Date Fri, 03 Mar 2017 00:28:51 GMT
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 (Oleksandr) Diachenko <
odiachenko@pivotal.io> wrote:

> 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 <jroberts@pivotal.io> 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 <
> > odiachenko@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 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 to be clean.
> > >
> > > Regards, Alex.
> > >
> > > On Thu, Mar 2, 2017 at 4:05 PM, Jon Roberts <jroberts@pivotal.io>
> wrote:
> > >
> > > > 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 updating
> > Ambari.
> > > >
> > > > Example:
> > > > hawq config -c hawq_rm_stmt_vseg_memory -v 16gb
> > > > INFO: Updated Ambari with hawq_rm_stmt_vseg_memory=16gb
> > > > or
> > > > hawq config -c hawq_rm_stmt_vseg_memory -v 16gb
> > > > WARN: Failed to update Ambari with hawq_rm_stmt_vseg_memory=16gb.
> > Please
> > > > update Ambari credentials manually to retain this configuration
> change
> > > > after a restart.
> > > >
> > > > The implementation would require interacting with the Ambari APIs and
> > > also
> > > > storing the credentials in an encrypted file on the HAWQ Master.
> > > >
> > > > Thoughts?
> > > >
> > > >
> > > > Jon Roberts
> > > > Principal Engineer | jroberts@pivotal.io | 615-426-8661
> > > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message