-
Notifications
You must be signed in to change notification settings - Fork 133
Upgrade to Spark 3.4.0 #235
Conversation
|
@microsoft-github-policy-service agree company="PulsePoint" |
|
@pp-akursar The change looks good. can u attach test results on 3.4.0. |
shivsood
left a comment
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.
Please add test results for 3.4 run. Post that this can be merged.
|
Please review and build! :) |
|
Test results on Spark 3.4.0 - Pass. Run : /*
val test_obj = new SparkConnTest("connectoradmin", "", "", "", "com.microsoft.sqlserver.jdbc.spark", "testconn","", "0", "false".toBoolean, "database.windows.net", 1433,""); Results: Passed |
|
Test Pass: Reliability Mode on. /*
Test : test_obj.test_sqlmaster_reliable_connector() Results : Pass test_isolation_level : SNAPSHOT succeded |
| | Spark 3.0.x compatible connector | `com.microsoft.azure:spark-mssql-connector_2.12:1.1.0` | 2.12 | | ||
| | Spark 3.1.x compatible connector | `com.microsoft.azure:spark-mssql-connector_2.12:1.2.0` | 2.12 | | ||
| | Spark 3.3.x compatible connector | `com.microsoft.azure:spark-mssql-connector_2.12:1.3.0` | 2.12 | | ||
| | Spark 3.4.x compatible connector | `com.microsoft.azure:spark-mssql-connector_2.12:1.4.0` | 2.12 | |
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.
Might also need to add spark 3.4 in Versions Supported
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.
yes, as we release the beta.
| <profiles> | ||
| <profile> | ||
| <id>spark33</id> | ||
| <id>spark34</id> |
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.
@shivsood Could you confirm that 3.4 spark DBR environment could not use 3.3 connector? If 3.4 DBR could still use 3.3 connector, then there is no need for a new release maybe?
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.
1.3.0-BETA release ( Spark 3.3) throws an exception for get schema type with DBR Spark 3.4.0.
|
Nice! thanks for reacting this quickly. |
|
@shivsood , can you tell us when the beta will be released and available through maven? We are wondering whether we should revert back to DBR 12.2 for now or if we can just wait a couple more days and switch to the new connector. And can we assume that for 3.3 it will stay 1.3.0-BETA? Also, it would be nice if the README could be updated in these two places (even for the previous release):
And 👍 for your work! |
|
Hello, Thanks :) |
|
@pp-akursar / @shivsood When are we planning to GA release this version It highly needed, You can also redirect me to concerning person who can better answer. |
|
Should azure databricks customers contact Azure support? It would be great to get GA versions of the connector. The default JDBC connector is not as fast. (even with the batchsize option/customization) What team at Microsoft sponsors this project? Is it HDInsight? Or Synapse? |
Changes similar to those of the previous upgrade to 3.3 at #197
Fixes #227, specifically
java.lang.NoSuchMethodError: 'org.apache.spark.sql.types.StructType org.apache.spark.sql.execution.datasources.jdbc.JdbcUtils$.getSchema(java.sql.ResultSet, org.apache.spark.sql.jdbc.JdbcDialect, boolean)'