Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/16255
@windpiger I am not sure that this is an analysis problem. I suspect that
optimizer is messing up the query. Could you pinpoint the rule that causes the
issue? Tip: in the spark shell (`./build/sbt sparkShell`) use
`sc.setLogLevel("TRACE")`, and that will print all rules being applied.
---
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]
