Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/20057
Our overwrite semantics is confusing to most. We need to correct it in the
next release, i.e., Spark 2.4.
Even if we try our best to keep the schema of the original table, the
actual CREATE TABLE statements still take many vendor-specific info. It is hard
for us to rebuild all of them. I can understand your use case for truncate.
I am sorry this will not be part of Spark 2.3 release. We will include it
in the next release. You can still do the change in your forked Spark.
Just feel free to let us know if you find anything that we should do in
Spark SQL JCBC to match the corresponding ones in SQOOP. Thanks!
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
