Skip to content

Allow direct local client connections to select a binary version - #500

Open
sdairs wants to merge 1 commit into
issue-466-local-client-selectorsfrom
issue-469-direct-client-version
Open

Allow direct local client connections to select a binary version#500
sdairs wants to merge 1 commit into
issue-466-local-client-selectorsfrom
issue-469-direct-client-version

Conversation

@sdairs

@sdairs sdairs commented Aug 24, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • add direct-only local client --version <exact-installed-version> binary selection without changing the configured default
  • retain default-only resolution when direct --version is omitted, with no zero/one/multiple-install guessing and actionable missing/stale errors
  • preserve named-server metadata version selection and document connection selection separately from local binary selection
  • cover the parser and subprocess default/installed/explicit-version matrices

Closes #469

Verification

  • cargo fmt --all --check
  • cargo build -p clickhousectl
  • cargo test -p clickhousectl (756 passed)
  • cargo clippy -p clickhousectl --all-targets -- -D warnings

Stack

@sdairs sdairs changed the title Allow direct client binary selection Allow direct local client connections to select a binary version Aug 24, 2026
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.

Allow direct local client connections to select a binary version

1 participant