fwc commented on code in PR #56190:
URL: https://github.com/apache/spark/pull/56190#discussion_r3454408680
##########
sql/connect/server/src/test/scala/org/apache/spark/sql/connect/DataSourceV2DataFrameConnectSuite.scala:
##########
@@ -34,7 +34,7 @@ import
org.apache.spark.sql.connector.catalog.{CachingInMemoryTableCatalog, InMe
* this class only provides the Connect-specific session, catalog access, and
result comparison.
*/
class DataSourceV2DataFrameConnectSuite
- extends SparkConnectServerTest
+ extends SessionQueryTest
Review Comment:
Is there a clear 'ideal way' for how which session semantics to provide?
Per-testcase would imply quite a bit of overhead, right?
Maybe we could leave guarantees around sessions explicitly 'undefined' to
for potential future optimizations?
(e.g. parallel execution of testscases in different session)
--
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]
