Github user bolkedebruin commented on the issue:
https://github.com/apache/spark/pull/19911
This is documented behavior for inherited tables. A select does the exact
same thing. Basically spark is changing the expected behavior, i.e. one
connects to a Postgres database this behavior is expected.
I donât think spark should interfere with how the database should
respond. If you use inherited tables you cascades, except for âdropâ. Think
about about it are we limiting selects by using âonlyâ to not have results
from inherited tables?
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
