Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/9202#issuecomment-152588761
@rick-ibm, thanks for working on this. With the Spark Summit just wrapping
up and code freeze for 1.6 tomorrow I don't think there is going to be a lot of
review bandwidth for a patch this large until after the release. While it
would be nice to secure things, this doesn't seem like a particularly high
priority vulnerability since any user that is creating a dataframe by querying
JDBC must have the credentials already and could just open their own connection.
I haven't looked closely at the implementation, but one high level question
is whether this is breaking the use case where a users gives a subquery instead
of a table name (i.e. `dbtable = (SELECT ...)`.) This is an important part of
the API that we can't break.
---
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
