Bump to version 4.2.7#797
Open
jprakash-db wants to merge 1 commit into
Open
Conversation
Signed-off-by: Jothi Prakash <jothi.prakash@databricks.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bump version to
4.2.7and add the4.2.7section toCHANGELOG.md.Notable changes since v4.2.6
use_kernel=True) — routes execution through the Databricks SQL kernel via PyO3, with TSparkParameter binding, Thrift backend feature parity, and_use_arrow_native_complex_typessupport (feat(backend/kernel): add use_kernel=True flag — route through the Rust kernel via PyO3 #787, feat(backend/kernel): wire TSparkParameter through to kernel bind_param #789, feat(backend/kernel): match Thrift backend's user-visible surface #793, feat(backend/kernel): honour _use_arrow_native_complex_types via kernel's complex_types_as_json post-processor #795)_respect_server_retry_after_headerretry mode that only retries 429/503 when the server sends aRetry-Afterheader — prevents duplicate side effects for non-idempotent operations (Add_retry_server_directed_onlymode for Retry-After header compliance #756)TokenFederationProviderto report inner auth mechanism/flow (Telemetry: unwrap TokenFederationProvider to report inner auth mech/flow #781)Test plan
pytest tests/unit/passes locally (751 passed, 4 skipped)universe/peco/correctness/pythonpassing — running on https://github.com/databricks-eng/universe/pull/1967448This pull request was AI-assisted by Isaac.