"Hive on Spark" uses Spark purely as execution engine. It would not get the
benefits of codegen and other optimizations of Spark.
If it is mainly for testing, OOTB parameters should work without issues.
However, Tez has lot better edge than Hive on Spark.
Some of the areas where Hive on Spark ne
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
?Yes. That's right. In secure mode, the streaming connection will set
hive.metastore.sasl.enabled to true which will create an UGI assuming transport
so all thrift calls are done using logged in user.
Thanks and Regards
Prasanth Jayachandran
From: Stig Rohde Døs
Thanks Prasanth. Is the automatic authentication a property of the
underlying MetaStoreClient?
Den ons. 13. mar. 2019 kl. 08.34 skrev Prasanth Jayachandran <
pjayachand...@hortonworks.com>:
> Hi
>
> If you are logged in, the hive streaming ingest API will use doAs for all
> metastore calls automa
Hi
If you are logged in, the hive streaming ingest API will use doAs for all
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.
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
