Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/19911#discussion_r155332414
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/jdbc/PostgresDialect.scala ---
@@ -100,5 +100,5 @@ private object PostgresDialect extends JdbcDialect {
}
- override def isCascadingTruncateTable(): Option[Boolean] = Some(true)
+ override def isCascadingTruncateTable(): Option[Boolean] = Some(false)
--- End diff --
@danielvdende .
Actually, I proposed TRUNCATE version as an optimized version of this
operation.
If DROP TABLE failed with the same reasons, it seems to be legitimate for
some reasons (your configurations or previleges)
BTW, if you enables this, does it solve your situation?
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
