Skip to content

Antalya 26.3 port - improvements for cluster requests#1687

Open
zvonand wants to merge 3 commits intoantalya-26.3from
feature/antalya-26.3/pr-1414-1
Open

Antalya 26.3 port - improvements for cluster requests#1687
zvonand wants to merge 3 commits intoantalya-26.3from
feature/antalya-26.3/pr-1414-1

Conversation

@zvonand
Copy link
Copy Markdown
Collaborator

@zvonand zvonand commented Apr 23, 2026

Cherry-picked from #1414.

Changelog category (leave one):

  • Not for changelog

Frontports for Antalya 26.1

CI/CD Options

Exclude tests:

  • Fast test
  • Integration Tests
  • Stateless tests
  • Stateful tests
  • Performance tests
  • All with ASAN
  • All with TSAN
  • All with MSAN
  • All with UBSAN
  • All with Coverage
  • All with Aarch64
  • All Regression
  • Disable CI Cache

Regression jobs to run:

  • Fast suites (mostly <1h)
  • Aggregate Functions (2h)
  • Alter (1.5h)
  • Benchmark (30m)
  • ClickHouse Keeper (1h)
  • Iceberg (2h)
  • LDAP (1h)
  • Parquet (1.5h)
  • RBAC (1.5h)
  • SSL Server (1h)
  • S3 (2h)
  • S3 Export (2h)
  • Swarms (30m)
  • Tiered Storage (2h)

…ous_hashing

26.1 Antalya port - improvements for cluster requests
@zvonand zvonand added releasy Created/managed by RelEasy ai-resolved Port conflict auto-resolved by Claude labels Apr 23, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 23, 2026

Workflow [PR], commit [3be7196]

@zvonand zvonand changed the title Antalya 26.3: 26.1 Antalya port - improvements for cluster requests Antalya 26.3 port - improvements for cluster requests Apr 24, 2026
std::optional<Int64> rows_count;
std::optional<Int64> bytes_size;
std::optional<Int64> nulls_count;
std::optional<DB::Range> hyperrectangle;
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

This field was removed between 26.1 and 26.3 (ClickHouse#98231), need code refactoring to use new place with min/max column values

Removes the `hyperrectangle` field from `DB::Iceberg::ColumnInfo` that
was re-added during the frontport. The field was removed upstream in
PR ClickHouse#98231, which relocated
raw min/max bounds to `ParsedManifestFileEntry::value_bounds`. The
`DataFileMetaInfo` Iceberg constructor now deserializes those bounds via
the shared `deserializeFieldFromBinaryRepr` helper (moved from
`ManifestFileIterator.cpp` to `IcebergFieldParseHelpers`).

Addresses @ianton-ru's comment at #1687 (comment).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ai-resolved Port conflict auto-resolved by Claude antalya-26.3 releasy Created/managed by RelEasy

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants