pan3793 opened a new pull request, #53230:
URL: https://github.com/apache/spark/pull/53230

   <!--
   Thanks for sending a pull request!  Here are some tips for you:
     1. If this is your first time, please read our contributor guidelines: 
https://spark.apache.org/contributing.html
     2. Ensure you have added or run the appropriate tests for your PR: 
https://spark.apache.org/developer-tools.html
     3. If the PR is unfinished, add '[WIP]' in your PR title, e.g., 
'[WIP][SPARK-XXXX] Your PR title ...'.
     4. Be sure to keep the PR description updated to reflect all changes.
     5. Please write your PR title to summarize what this PR proposes.
     6. If possible, provide a concise example to reproduce the issue for a 
faster review.
     7. If you want to add a new configuration, please read the guideline first 
for naming configurations in
        
'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
     8. If you want to add or modify an error type or message, please read the 
guideline first in
        'common/utils/src/main/resources/error/README.md'.
   -->
   
   ### What changes were proposed in this pull request?
   <!--
   Please clarify what changes you are proposing. The purpose of this section 
is to outline the changes and how this PR fixes the issue. 
   If possible, please consider writing useful notes for better and faster 
reviews in your PR. See the examples below.
     1. If you refactor some codes with changing classes, showing the class 
hierarchy will help reviewers.
     2. If you fix some SQL features, you can provide some references of other 
DBMSes.
     3. If there is design documentation, please add the link.
     4. If there is a discussion in the mailing list, please add the link.
   -->
   The Connect JDBC driver is built on top of the Connect JVM client, so it 
should declare the Connect JVM client as the dependency, and Maven will resolve 
transitive deps correctly.
   
   Note, many RDBMS products provide a single no-deps JDBC driver jar to 
simplify downstream projects' integration, while this is not achieved at the 
current stage, and may be considered in the future.
   
   ### Why are the changes needed?
   <!--
   Please clarify why the changes are needed. For instance,
     1. If you propose a new API, clarify the use case for a new API.
     2. If you fix a bug, you can clarify why it is a bug.
   -->
   Fix Connect JDBC driver dependency management.
   
   For example, it should not pull protobuf libs which are already shaded in 
connect-jdbc-client.
   
   
https://mvnrepository.com/artifact/org.apache.spark/spark-connect-client-jdbc_2.13/4.1.0-preview4
   
   ### Does this PR introduce _any_ user-facing change?
   <!--
   Note that it means *any* user-facing change including all aspects such as 
new features, bug fixes, or other behavior changes. Documentation-only updates 
are not considered user-facing changes.
   
   If yes, please clarify the previous behavior and the change this PR proposes 
- provide the console output, description and/or an example to show the 
behavior difference if possible.
   If possible, please also clarify if this is a user-facing change compared to 
the released Spark versions or within the unreleased branches such as master.
   If no, write 'No'.
   -->
   No, the Connect JDBC driver is not released yet.
   
   ### How was this patch tested?
   <!--
   If tests were added, say they were added here. Please make sure to add some 
test cases that check the changes thoroughly including negative and positive 
cases if possible.
   If it was tested in a way different from regular unit tests, please clarify 
how you tested step by step, ideally copy and paste-able, so that other 
reviewers can test and check, and descendants can verify in the future.
   If tests were not added, please describe why they were not added and/or why 
it was difficult to add.
   If benchmark tests were added, please run the benchmarks in GitHub Actions 
for the consistent environment, and the instructions could accord to: 
https://spark.apache.org/developer-tools.html#github-workflow-benchmarks.
   -->
   Pass GHA, plus manual verifications.
   
   - Checked the effective `pom.xml` which is located at 
`sql/connect/client/jdbc/dependency-reduced-pom.xml` after compiling, only one 
compile scope dep.
   
     ```xml
     <dependency>
       <groupId>org.apache.spark</groupId>
       <artifactId>spark-connect-client-jvm_2.13</artifactId>
       <version>4.2.0-SNAPSHOT</version>
       <scope>compile</scope>
     </dependency>
     ```
   
   - Verified locally by running tests using Maven/SBT
   
     Maven
     ```
     build/mvn -Phive,hive-thriftserver -pl sql/connect/client/jdbc -am clean 
install -DskipTests
     build/mvn -Phive,hive-thriftserver -pl sql/connect/client/jdbc test
     ```
     
     SBT
     ```
     build/sbt -Phive,hive-thriftserver "connect-client-jdbc/test"
     ```
   
   - Verified CLI cases with BeeLine by creating a binary release artifact 
using Maven/SBT
   
     Launch a Connect Server first, then
     ```
     dev/make-distribution.sh [--sbt-enabled] -Phive,hive-thriftserver
     cd dist
     SPARK_CONNECT_BEELINE=1 bin/beeline -u jdbc:sc://localhost:15002 -e 
"select 'Hello, Spark Connect!', version() as server_version;"
     ```
   
   ### Was this patch authored or co-authored using generative AI tooling?
   <!--
   If generative AI tooling has been used in the process of authoring this 
patch, please include the
   phrase: 'Generated-by: ' followed by the name of the tool and its version.
   If no, write 'No'.
   Please refer to the [ASF Generative Tooling 
Guidance](https://www.apache.org/legal/generative-tooling.html) for details.
   -->
   No.


-- 
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]

Reply via email to