Skip to content

feat: support geospatial results on the kernel path - #534

Draft
cathleeny wants to merge 1 commit into
databricks:mainfrom
cathleeny:feat/geospatial-results
Draft

cathleeny wants to merge 1 commit into
databricks:mainfrom
cathleeny:feat/geospatial-results

Conversation

@cathleeny

Copy link
Copy Markdown
Collaborator

Summary

  • add the kernel-only geospatialAsString connection option
  • expose EWKT strings in string mode and canonical { srid, wkb: Buffer } values in binary mode
  • keep the option entirely client-side (it is never forwarded to SEA)
  • update the generated native declaration and pin local kernel builds to the exact kernel dependency commit below

Dependency

Depends on databricks/databricks-sql-kernel#361 at ad3bc6993bca95b810839feade77ccd0ab98ece5.

Keep this PR in draft until #361 is merged and native kernel packages containing that commit are available. The released optional native packages remain at 1.1.0 today; this PR intentionally does not invent a prerelease package version.

Validation

npm run type-check also reaches an existing token-federation example self-import harness failure; the production npm run build type-check is green and this change does not touch that harness.

Signed-off-by: Cathleen Yan <58714163+cathleeny@users.noreply.github.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant