Ok, that is a valid reason.
On Thu, Nov 7, 2019 at 2:03 AM Bhavani Sudha
wrote:
> Ah okay. That is a valid concern. Dint think about admin management for
> Hive dbs.
>
> Thanks,
> Sudha
>
> On Wed, Nov 6, 2019 at 12:28 PM Balaji Varadarajan
> wrote:
>
> > I have a different opinion on this.
Ah okay. That is a valid concern. Dint think about admin management for
Hive dbs.
Thanks,
Sudha
On Wed, Nov 6, 2019 at 12:28 PM Balaji Varadarajan
wrote:
> I have a different opinion on this. Usually, in production deployments
> (atleast whatever I am aware of), database is generally managed
I have a different opinion on this. Usually, in production deployments
(atleast whatever I am aware of), database is generally managed at the
org/group level. Privacy policies like ACLs are usually done at database
level and would need first level management by admins. With such a setup,
its
+1 I think we should create db if it does not exist.
On Tue, Nov 5, 2019 at 11:08 PM Pratyaksh Sharma
wrote:
> Hi,
>
> While doing hive sync using HiveSyncTool, we first check if the target
> table exists in hive. If not, we try to create it. However in this flow, if
> the database itself does
Hi,
While doing hive sync using HiveSyncTool, we first check if the target
table exists in hive. If not, we try to create it. However in this flow, if
the database itself does not exist, we do not create the database before
creating hive table, which results in exception like below -
