Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/17241
@hvanhovell From an end user perspective, there may be two major
differences:
1. If the nested level exceed the value, the user will see a explict
message about what caused the failure, instead of an exception that may be
confusing;
2. We don't have to wait for a long time to trigger a exception, we can
fail earlier by setting a proper value for the property
`spark.sql.view.maxNestedViewDepth`.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]