Skip to content

feat(catalog/rest): use the REST spec User-Agent format - #2516

Merged
laskoviymishka merged 1 commit into
apache:mainfrom
rahulsmahadev:user-agent-format
Nov 11, 2026
Merged

laskoviymishka merged 1 commit into
apache:mainfrom
rahulsmahadev:user-agent-format

Conversation

@rahulsmahadev

Copy link
Copy Markdown
Contributor

The Iceberg REST catalog spec now recommends a standard User-Agent format (apache/iceberg#17727). iceberg-go now sends iceberg-go/<version> (go <go version>), for example iceberg-go/0.4.0 (go 1.27.1), instead of GoIceberg/<version>.

  • The leading v of the module version is dropped, so all Iceberg clients send plain versions.
  • A build without a module version sends unknown as the version.
  • Headers set by the caller still take precedence over the default.

Testing: TestDefaultUserAgent, plus the existing header tests updated for the new value.

This pull request and its description were written by Isaac.

Send iceberg-go/<version> (go <go version>) as the default User-Agent,
following the format recommended by the REST catalog spec
(apache/iceberg#17727). Headers configured by the caller still take
precedence over the default.

@laskoviymishka laskoviymishka left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @rahulsmahadev for picking this up right after apache/iceberg#17727 landed. The new value follows the spec's product/version (runtime version) shape with the iceberg-go token the spec lists, and TestDefaultUserAgent covers both the v strip and the unknown fallback.

@laskoviymishka
laskoviymishka merged commit df0fe9a into apache:main Nov 11, 2026
16 checks passed
@laskoviymishka

Copy link
Copy Markdown
Contributor

@rahulsmahadev welcome to contributors club! <3

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.

2 participants