-
Notifications
You must be signed in to change notification settings - Fork 29k
[WIP][SPARK-42240][INFRA][CONNECT][TESTS] Move ClientE2ETestSuite into a separate module and add new GA task to test shaded jvm client with maven
#39807
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| <version>${guava.version}</version> | ||
| <scope>compile</scope> | ||
| </dependency> | ||
| <!-- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
move ClientE2ETestSuite out of client jvm, we can revert this change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If necessary, I can do this change in a separate pr
connector/connect/client/jvm/pom.xml
Outdated
| <artifactSet> | ||
| <includes> | ||
| <include>com.google.guava:*</include> | ||
| <include>io.grpc:*:</include> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should revert this change after #39789 merged
| with: | ||
| distribution: temurin | ||
| java-version: ${{ matrix.java }} | ||
| - name: Build and Test with Maven |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reason for using maven for build and test is that in the current dependency configuration way, I don't know how SBT fetch assembly connect client jar
|
Test first, will update pr description later |
| sys.props.getOrElse("spark.test.home", sys.env("SPARK_HOME")) | ||
| } | ||
| private val isDebug = System.getProperty(DEBUG_SC_JVM_CLIENT, "false").toBoolean | ||
| private val isDebug = System.getProperty(DEBUG_SC_JVM_CLIENT, "true").toBoolean |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will revert this change after all test passed
This comment was marked as outdated.
This comment was marked as outdated.
ClientE2ETestSuite into a separate module and add new GA task to test shaded jvm client with maven
...m-e2e-tests/src/test/scala/org/apache/spark/sql/connect/client/util/RemoteSparkSession.scala
Outdated
Show resolved
Hide resolved
|
Because the ClientE2ETestSuite requires a shaded server jar, the direct execution of or will still fail, which is no different from without this pr |
|
Need wait some days, because |
What changes were proposed in this pull request?
The main change of this pr as follows:
ClientE2ETestSuiteinto a new separate module, the new module namedconnect-jvm-e2e-tests, and add a new profile namedconnect-client-teststo activate this module. The new profile is added because the current test way of this module is cumbersome and it is not easy to build and test by default.we need the follow steps for the new module test with maven
or
It seems simpler to use sbt for test, but in the current dependency management way, using sbt to fetch the no-shaded connect-client jar cannot achieve the purpose of testing both the shaded client jar and the shaded server jar in the E2E tests.
Add a new GA task named
connect-jvm-e2e-tests, this task use maven to test shadedconnect-client-jvm. Under the current dependency management way, if we can find out how to fetch the assembly jar by sbt, we should change it to a more efficient sbt test mode.Remove
repltest dependency fromconnector/connect/client/jvm/pom.xmldue toClientE2ETestSuitemove into separate module.Why are the changes needed?
We should do E2E test with shaded client jar and shaded server jar. Before this pr,
ClientE2ETestSuiteis inconnect-client-jvmmodule and the test will using shaded server jar and no-shaded client jar. After this pr, the test purpose can be achieved by using maven, but the test way using sbt needs to be further explored.Does this PR introduce any user-facing change?
No
How was this patch tested?
Scala 2.13 using maven
Scala 2.12 using sbt
Scala 2.13 using sbt