Antalya 26.3 Backport of #100645 - Parse record_count and size_bytes fields from iceberg manifest file

[mkmkme]

Changelog category (leave one):

• Improvement

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

Object information used for parsing data files in iceberg now contains the number of file rows and file size in bytes parsed from manifest file (ClickHouse#100645 by @divanik).

Documentation entry for user-facing changes

...

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)

[github-actions]

Workflow [PR], commit [3cb64e5]

[ianton-ru]

Am I right that writing in log with 'test' level is an only place, where new data are used?

[alsugiliazova]

Audit: PR #1776 — Antalya 26.3 Backport of #100645 — Parse record_count and size_bytes fields from iceberg manifest file

AI audit note: generated by AI (Cursor agent, audit-review skill).

Confirmed defects

No confirmed defects in reviewed scope.

[ianton-ru]

LGTM, but I don't understand a value of this PR. It makes a lot of work only to write two lines in log with 'test' level. Or I missed something.

[alsugiliazova]

Verification: PR #1776

tats_logging(storages3× format-version1/2×use_view False/True` = 4 cases).

PR-added tests — all GREEN

4 parametrized cases × 3 integration jobs = 12 OK runs, 0 failures.

Job	Cases run	Status
Integration tests (amd_asan, db disk, old analyzer, 4/6)	4	OK
Integration tests (amd_binary, 5/5)	4	OK
Integration tests (arm_binary, distributed plan, 2/4)	4	OK

All four parametrizations pass on every job:

• [s3-1-False], [s3-1-True] — format-version 1, with/without view
• [s3-2-False], [s3-2-True] — format-version 2, with/without view

The new manifest-file stats path has clean positive coverage on both Iceberg spec versions and on plain-table / view-wrapped reads.

Note: the new gtest gtest_datalake_table_state_serde is built into the unit-tests binary; the unit-tests job ran green in this CI rollup.

CI overview (head commit)

• PR test workflow: 46 success / 50 skipped / 0 failure — fully GREEN at the PR test workflow level.
• Regression workflow: 29 success / 67 skipped / 4 failure (chronic baseline).
• One pending action_required job (queue/auth).

Test-level failures in DB

Zero. No test_status='FAIL' rows on this commit.

Regression-workflow failures (chronic baseline on antalya-26.3)

Suite	Fails
Swarms (Aarch64 + Release)	227
Parquet (Aarch64 + Release)	34
S3Export partition (Aarch64 + Release)	20
S3Export part (Aarch64 + Release)	16

Same fingerprint as sibling antalya-26.3 PRs (1783, 1775, 1773, 1772, 1771, 1770, 1769, …). No new failure modes.

Caveat — partial frontport

PR lands on antalya-26.3 while companion features from antalya-26.1 are still being frontported in parallel. Final re-verify recommended once the rest of the bundle lands.

Verdict

Safe to merge.

• New integration test test_iceberg_file_stats_logging passes 100% (12/12 integration runs) across all 4 parametrizations and 3 integration jobs.
• New gtest for datalake_table_state serde compiles and runs green.
• Zero test-level FAIL rows on this head.
• All remaining red checks are the recurring antalya-26.3 chronic regression baseline (Swarms / Parquet / S3Export), shared with sibling PRs.