Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/19911
1. Like the other DBMSs, Spark assumes that `TRUNCATE` can be used **only
when** it doesn't make a change on the other tables.
> I donât think spark should interfere with how the database should
respond.
2. It's documented. So, we marked `override def isCascadingTruncateTable():
Option[Boolean] = Some(true)` for PostgreSQL. We don't want any side-effects in
this Spark operations like the other DBMSs.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
