You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hive.apache.org by Furcy Pin <fu...@flaminem.com> on 2014/06/30 09:15:22 UTC

Multiple insert on same table with INSERT OVERWRITE + INSERT INTO ?

Hi all,


Does anyone know what is the expected behavior on a query like this :

FROM source
INSERT OVERWRITE TABLE dest
SELECT *
INSERT INTO TABLE dest
SELECT *

is it the same as

FROM source
INSERT INTO TABLE dest
SELECT *
INSERT OVERWRITE TABLE dest
SELECT *

?

I'm asking because I ran a query looking like the first one on hive 0.12,
and it seems to me that the OVERWRITE was completely ignored :
I mean that the old data (which was there before the query) was still
there...
And I checked, it was no access right problem, table was 777, no sticky
bits
(I already had issues with ghost data on OVERWRITE because of it)

One last thing : my table was partitioned and I used nonstrict dynamic
partitioning,
perhaps it had an impact on the behavior too.

Thanks,

Furcy

Re: Multiple insert on same table with INSERT OVERWRITE + INSERT INTO ?

Posted by Furcy Pin <fu...@flaminem.com>.
After doing some simple tests, multiple insert into the same partition of
the same table is disallowed by hive,
except when using dynamic partitioning...

In that specific case, I don't know if the behavior should be considered as
an undefined behavior, a feature or a bug...

What do you think?



2014-06-30 9:15 GMT+02:00 Furcy Pin <fu...@flaminem.com>:

> Hi all,
>
>
> Does anyone know what is the expected behavior on a query like this :
>
> FROM source
> INSERT OVERWRITE TABLE dest
> SELECT *
> INSERT INTO TABLE dest
> SELECT *
>
> is it the same as
>
> FROM source
> INSERT INTO TABLE dest
> SELECT *
> INSERT OVERWRITE TABLE dest
> SELECT *
>
> ?
>
> I'm asking because I ran a query looking like the first one on hive 0.12,
> and it seems to me that the OVERWRITE was completely ignored :
> I mean that the old data (which was there before the query) was still
> there...
> And I checked, it was no access right problem, table was 777, no sticky
> bits
> (I already had issues with ghost data on OVERWRITE because of it)
>
> One last thing : my table was partitioned and I used nonstrict dynamic
> partitioning,
> perhaps it had an impact on the behavior too.
>
> Thanks,
>
> Furcy
>
>
>
>