Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15925
BTW optimizer technically shouldn't have anything to do with correctness,
so it shouldn't be the optimizer's job to make sure jdbc can connect. I'd just
generate the SQL to "false" (depending on how we define the behavior).
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
