The standalone metastore released in 3.0 is the exact same metastore
released with Hive 3.0. The only differences are in the install tool
'schematool' and the start and stop script. Hive 3 is being used in
production a number of places. I don't know if anyone is running the
metastore alone in pr
Thank you for the revert.
We do have a use case to provide tenant / bucket specific keys for a tenant
user session, without having to restart the MetaStore server when a new
tenant is provisioned.
Nevertheless, let me explore a bit around Sentry / Ranger too.
Thank you,
Sandhya
On Thu, Jul 12,
AFAIK currently, s3 keys cannot be session specific currently. They are
loaded by the metastore server when it starts and it cannot be modified
without a metastore server restart. In order to do this we will have make
some code changes. I had created HIVE-16913 for this long time back but
never got
