# ES-Hadoop 2.0.2 jars and INSERT OVERWRITE

**URL:** <https://discuss.elastic.co/t/es-hadoop-2-0-2-jars-and-insert-overwrite/24091>\
**Category:** Elasticsearch\
**Tags:** es-hadoop\
**Created:** [June 22, 2015, 1:08pm UTC](https://discuss.elastic.co/t/es-hadoop-2-0-2-jars-and-insert-overwrite/24091 "2015-06-22T13:08:20Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![aken](https://avatars.discourse-cdn.com/v4/letter/a/b38774/32.png) [@aken](https://discuss.elastic.co/u/aken)\
**Post date:** [June 22, 2015, 1:32pm UTC](https://discuss.elastic.co/t/es-hadoop-2-0-2-jars-and-insert-overwrite/24091/3 "2015-06-22T13:32:04Z")

</div>

Hallo Costin,

Thanks for your reply. The standard Hive behaviour with internal tables (certainly with partitions) is that Hive empties the target location/partition and writes the new data afresh. With EXTERNAL TABLES that is a grey area as the data does not strictly "belong" to Hive, so I can understand why a delete does not happen (I would think the most elegant implementation would be to control this behaviour via a property, as is done with e.g.'es.index.auto.create', although DELETEs are there in Hive 0.14).

But at least I know that is expected behaviour! Thanks for your help.

Andrew

---

_[View the full topic](https://discuss.elastic.co/t/es-hadoop-2-0-2-jars-and-insert-overwrite/24091)._