Thanks for the explanation.
Den ons. 13. mar. 2019 kl. 08.54 skrev Prasanth Jayachandran <
pjayachand...@hortonworks.com>:
> Hi,
>
> The hive-hcatalog-streaming client (HiveEndpoint) took a
> UserGroupInformation in the constructor for connections, and automatically
> wrapped calls as necessary w
Rohde Døssing
Sent: Wednesday, March 13, 2019 12:44 AM
To: user@hive.apache.org
Subject: Re: Hive-streaming security
Thanks Prasanth. Is the automatic authentication a property of the underlying
MetaStoreClient?
Den ons. 13. mar. 2019 kl. 08.34 skrev Prasanth Jayachandran
mailto:pjaya
t; metastore calls automatically using the logged in user.
>
>
> Thanks and Regards
> Prasanth Jayachandran
> --
> *From:* Stig Rohde Døssing
> *Sent:* Wednesday, March 13, 2019 12:19 AM
> *To:* user@hive.apache.org
> *Subject:* Re: Hive-streaming
@hive.apache.org
Subject: Re: Hive-streaming security
Sorry, should have looked harder. The docs say to log in before invoking the
API. I think this means I should be wrapping calls with doAs?
Den ons. 13. mar. 2019 kl. 08.09 skrev Stig Rohde Døssing
mailto:stigdoess...@gmail.com>>:
Hi,
The hive-hc
Sorry, should have looked harder. The docs say to log in before invoking
the API. I think this means I should be wrapping calls with doAs?
Den ons. 13. mar. 2019 kl. 08.09 skrev Stig Rohde Døssing <
stigdoess...@gmail.com>:
> Hi,
>
> The hive-hcatalog-streaming client (HiveEndpoint) took a
> User
Hi,
The hive-hcatalog-streaming client (HiveEndpoint) took a
UserGroupInformation in the constructor for connections, and automatically
wrapped calls as necessary with UserGroupInformation.doAs.
I'm migrating an application from hive-hcatalog-streaming to
hive-streaming. There's no mention of sec
