Skip to content

25.8.16 Backport of #87258 - Fix 'Invalid dict indices bit width: 0' in parquet reader v3#1384

Merged
zvonand merged 1 commit intoreleases/25.8.16from
backports/25.8.16/872258
Feb 15, 2026
Merged

25.8.16 Backport of #87258 - Fix 'Invalid dict indices bit width: 0' in parquet reader v3#1384
zvonand merged 1 commit intoreleases/25.8.16from
backports/25.8.16/872258

Conversation

@mkmkme
Copy link
Collaborator

@mkmkme mkmkme commented Feb 9, 2026

Fix 'Invalid dict indices bit width: 0' in parquet reader v3

Changelog category (leave one):

  • Not for changelog (changelog entry is not required)

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

Fix 'Invalid dict indices bit width: 0' in parquet reader v3 (ClickHouse#87258 by @al13n321)

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)
  • Tiered Storage (2h)

Fix 'Invalid dict indices bit width: 0' in parquet reader v3
@mkmkme mkmkme added backport Backport 25.8 25.8 Altinity Stable 25.8.16 25.8.16 Stable 25.8.16.10001 25.8.16.10001 Stable labels Feb 9, 2026
@github-actions
Copy link

github-actions bot commented Feb 9, 2026

Workflow [PR], commit [8bde797]

@svb-alt svb-alt added 25.8.16.10001 25.8.16.10001 Stable and removed 25.8.16.10001 25.8.16.10001 Stable labels Feb 9, 2026
@zvonand zvonand merged commit 70d32da into releases/25.8.16 Feb 15, 2026
616 of 617 checks passed
@zvonand
Copy link
Collaborator

zvonand commented Feb 15, 2026

The change is trivial and the CI is green.

@Selfeer
Copy link
Collaborator

Selfeer commented Feb 16, 2026

All the checks are green based on the report: https://s3.amazonaws.com/altinity-build-artifacts/PRs/1384/8bde797fe8d56980bd876e6e168fb546bc09ed75/21825761747/ci_run_report.html

There are no tests attached to this PR, the comment of the author states the following:

(No test because I don't have an easy way to generate a test file. The one I looked at was 500 MB, produced by parquet-mr > version 1.15.2 (build 859eac165b08f927fa14590c33bc5f476405fb68).)

Attaching a large file and automating the process seems to be problematic for now but we do have a repro file that allows us to manually verify that the change fixed the issue.

Here is the query on upstream version without this change:

SELECT * FROM file('dict_repro.parquet') SETTINGS input_format_parquet_use_native_reader_v3 = 1

65409 rows in set. Elapsed: 0.084 sec. 

Received exception from server (version 25.8.15):
Code: 117. DB::Exception: Received from localhost:9000. DB::Exception: Invalid dict indices bit width: 0: read stage: MainData: column: mta_tax: (in file/uri /var/lib/clickhouse/user_files/dict_repro.parquet): While executing ParquetV3BlockInputFormat: While executing File. (INCORRECT_DATA)

After backport we don't get that issue and all other parquet auto test are also green as stated above:

SELECT * FROM file('dict_repro.parquet') SETTINGS input_format_parquet_use_native_reader_v3 = 1

Showed 1000 out of 167102565 rows.

167102565 rows in set. Elapsed: 5.147 sec. Processed 167.10 million rows, 23.66 GB (32.47 million rows/s., 4.60 GB/s.)
Peak memory usage: 4.25 GiB.

-------------------------------------------------

SELECT version()

Query id: ab5c4e1d-7ddc-4a25-9190-a41d589e0ab6

   ┌─version()──────────────────┐
1. │ 25.8.16.10001.altinitytest │
   └────────────────────────────┘

1 row in set. Elapsed: 0.001 sec.

@Selfeer Selfeer added the verified Verified by QA label Feb 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

25.8 25.8 Altinity Stable 25.8.16 25.8.16 Stable 25.8.16.10001 25.8.16.10001 Stable backport Backport verified Verified by QA

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants