Add native JSON type support for SQL Server 2025#28101
Add native JSON type support for SQL Server 2025#28101kirkhansen wants to merge 1 commit intotrinodb:masterfrom
Conversation
|
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Kirk Hansen.
|
4c0ebbf to
9d4e099
Compare
|
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Kirk Hansen.
|
9d4e099 to
7bdabeb
Compare
|
This pull request has gone a while without any activity. Ask for help on #core-dev on Trino slack. |
|
Closing this pull request, as it has been stale for six weeks. Feel free to re-open at any time. |
814f905 to
901a6c1
Compare
|
@findepi Let me know if that's what you were after or not. Happy to make any fixes or adjustments as needed here. |
|
@kirkhansen please rebase on |
|
@kirkhansen please also squash all the commits because they all relate to each other. |
22ba0c6 to
a0bdea4
Compare
a0bdea4 to
9ecc663
Compare
|
@kirkhansen pls do push an empty commit to retrigger the build 🙏 - |
9ecc663 to
d9031d1
Compare
d9031d1 to
fa500be
Compare
Description
This PR adds support for SQL Server 2025's native JSON data type in the Trino SQL Server connector. Previously, JSON columns were filtered out due to the Microsoft JDBC driver not exposing them through
DatabaseMetaData.getColumns().Changes:
JsonTypemapping inSqlServerClientfor SQL Server's native JSON type (DATA_TYPE: -157/-159)pom.xmlto use Microsoft JDBC Driver 13.3.1 (includes PR Add support for json_path wildcard #2883 fix for JSON column visibility)Testing: All tests pass against SQL Server 2025-latest container (RTM-CU1)
Additional context and related issues
sp_columns_170)Release notes
(x) Release notes are required, with the following suggested text:
Related PRs