Repository navigation
Conversation
…tings Refreshes the snapshot to the live spec, which adds optional `useJsonNativeFormat` to `ClickPipeMySQLPipeSettings` and `ClickPipePostgresPipeSettings`. The field is create-only and organization-gated, so it is `Option<bool>` on all four types, with an optionality exemption on the Postgres request type, whose schema has no `required[]`. The CLI passes `None`, so its requests are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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.
Refs #1490. API PR for drift that appeared after #1482 was filed, stacked on #1489. CLI exposure follows in #1492.
clickhouse_cloud_openapi.json. The only spec change is the newuseJsonNativeFormatproperty onClickPipeMySQLPipeSettingsandClickPipePostgresPipeSettings.use_json_native_format: Option<bool>on those two request types and their*Responsetypes.("ClickPipePostgresPipeSettings", "useJsonNativeFormat"). That schema has norequired[], so the description fallback marks the field required. But it is create-only and must be enabled per organization, so a requiredboolwould sendfalsefrom every caller, as withiamRoleExternalId(AWS backup bucket create cannot succeed in orgs without the external-ID feature (iamRoleExternalId required by the library, rejected by the server) #1245). Not yet confirmed against the live API. The MySQL schema has arequired[]without it, so it needs no entry.use_json_native_format: None); seeCHANGELOG.md.None, so its requests are unchanged.spec_coverage_testpasses, and the live drift dry-run reports 0 actionable findings at the top of the stack.🤖 Generated with Claude Code
Note
Low Risk
Adds optional API model fields and spec sync; CLI behavior unchanged (
None). Postgres optionality exemption is noted as not yet live-verified.Overview
Adds
useJsonNativeFormatto the synced OpenAPI spec and Rust models for MySQL and Postgres ClickPipe create settings (ClickPipeMySQLPipeSettings,ClickPipePostgresPipeSettings, plus their*Responsetypes). Callers may setuse_json_native_format: Some(true)to land JSON source columns in native ClickHouseJSON(25.3+) instead ofString;Noneomits the field. The field is create-only and org feature-gated.Breaking: struct-literal builders must add
use_json_native_format: None. The openapi analyzer adds an optionality exemption for Postgres so the field is not treated as required (avoiding implicitfalsefor orgs without the feature). clickhousectl wiresNoneonly—no CLI flag yet. Tests cover omit/set serialization and response parsing; live pipe tests updated.Reviewed by Cursor Bugbot for commit 120f1a9. Bugbot is set up for automated code reviews on this repo. Configure here.