Skip to content

[build] Allow opting into rustls for Paimon HTTP clients - #1453

Open
naivedogger wants to merge 1 commit into
apache:mainfrom
naivedogger:optional-rustls
Open

naivedogger wants to merge 1 commit into
apache:mainfrom
naivedogger:optional-rustls

Conversation

@naivedogger

Copy link
Copy Markdown

Purpose

Closes #1451.

Paimon currently enables reqwest’s default TLS backend, which can introduce an OpenSSL build dependency on Linux. Making the backend selectable allows downstream crates to use rustls for Paimon’s HTTP clients as well.

Brief change log

Expose native-tls (default) and rustls as Cargo features. The rustls backend uses system certificate roots. Existing non-TLS reqwest features are retained.

Tests

Checked the Linux dependency graph with cargo tree: the default build includes openssl-sys; the build with --no-default-features --features rustls does not.

API and Format

Default builds retain native TLS. Applications that already set default-features = false and rely on HTTPS must explicitly enable native-tls or rustls when upgrading. Cargo features are additive, so another dependency can still enable native TLS for the same reqwest version.

Documentation

The getting-started guide includes a rustls configuration and the migration note for applications that disable default features.

Co-Authored-By: Codex <noreply@openai.com>
AI-Model: gpt-6
AI-Contributed/Feature: 25/25
AI-Contributed/UT: 0/0
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 applications to select rustls for Paimon HTTP clients

1 participant