Github user danielvdende commented on the issue:

    https://github.com/apache/spark/pull/20057
  
    I've made some changes to the code; the hardcoded `false` value for 
`cascade` in `JdbcDialects` is now replaced by a default value of 
`isCascadingTruncateTable`. This is also the case for each individual dialect, 
with a pattern match in the dialects for Postgres and Oracle, as they support 
the cascading behaviour. Curious to hear your thoughts on this @dongjoon-hyun 
@gatorsmile 


---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to