Thanks Shawn,
Yeah, I was talking about that. In that documentation didn't see any
authentication so was wondering if there were options to protect it. But
doesn't seem as you said.
Thanks

On Wed, 17 Apr 2019, 13:21 Shawn Weeks, <swe...@weeksconsulting.us> wrote:

> I think they misunderstood, your talking about this
> https://cwiki.apache.org/confluence/display/Hive/AdminManual+Metastore+Administration.
> As far as I know the only authentication it supports is Kerberos.
>
>
>
> Thanks
>
> Shawn
>
>
>
> *From:* Odon Copon <odonco...@gmail.com>
> *Sent:* Wednesday, April 17, 2019 3:16 AM
> *To:* user@hive.apache.org
> *Subject:* Re: Hive metastore service
>
>
>
> Hi,
>
> I don't know if I am not understanding properly the design, but, isn't
> there supposed to be a Hive metastore service that Hive server uses to
> access the metastore db?
>
>
>
> On Tue, 16 Apr 2019, 22:26 Mich Talebzadeh, <mich.talebza...@gmail.com>
> wrote:
>
> Try this
>
>
>
> Assuming that you are talking about Hive Thrift server
>
>
>
> beeline -u jdbc:hive2://rhes75:10099/default
> org.apache.hive.jdbc.HiveDriver *-n USERNAME -p PASSWORD*  -i
> /home/hduser/dba/bin/add_jars.hql'
>
>
>
> HTH
>
>
>
> Dr Mich Talebzadeh
>
>
>
> LinkedIn  
> *https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw
> <https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw>*
>
>
>
> http://talebzadehmich.wordpress.com
>
>
>
> *Disclaimer:* Use it at your own risk. Any and all responsibility for any
> loss, damage or destruction of data or any other property which may arise
> from relying on this email's technical content is explicitly disclaimed.
> The author will in no case be liable for any monetary damages arising from
> such loss, damage or destruction.
>
>
>
>
>
>
>
> On Tue, 16 Apr 2019 at 16:11, Odon Copon <odonco...@gmail.com> wrote:
>
> Hi,
>
> would be possible to add authentication to the Thrift Hive metastore
> service? like user and password?
>
> I cannot find any documentation on how to protect this endpoint.
>
> Thanks.
>
>

Reply via email to