cloud-fan commented on a change in pull request #34738:
URL: https://github.com/apache/spark/pull/34738#discussion_r767462841
##########
File path:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/jdbc/JDBCOptions.scala
##########
@@ -196,6 +196,10 @@ class JDBCOptions(
// This only applies to Data Source V2 JDBC
val pushDownLimit = parameters.getOrElse(JDBC_PUSHDOWN_LIMIT,
"false").toBoolean
+ // An option to allow/disallow pushing down query of top N into V2 JDBC data
source
+ // This only applies to Data Source V2 JDBC
+ val pushDownTopN = parameters.getOrElse(JDBC_PUSHDOWN_TOP_N,
"false").toBoolean
Review comment:
I'm wondering if we should just reuse the limit pushdown option, as it's
kind of a special case of LIMIT.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
