Skip to content

Write Parquet bloom filters#71681

Merged
al13n321 merged 13 commits intomasterfrom
bff
Feb 7, 2025
Merged

Write Parquet bloom filters#71681
al13n321 merged 13 commits intomasterfrom
bff

Conversation

@al13n321
Copy link
Copy Markdown
Member

@al13n321 al13n321 commented Nov 9, 2024

Changelog category (leave one):

  • Not for changelog (changelog entry is not required)

A pretty straightforward feature. Controlled by setting output_format_parquet_write_bloom_filter. Adds ~2 bytes per row+column (can't be compressed). E.g. +10% file size on test.hits. Disabled Enabled by default.

Also refactored write_page_index, it had a couple of bugs.

@robot-ch-test-poll robot-ch-test-poll added the pr-not-for-changelog This PR should not be mentioned in the changelog label Nov 9, 2024
@robot-ch-test-poll
Copy link
Copy Markdown
Contributor

robot-ch-test-poll commented Nov 9, 2024

This is an automated comment for commit 0e0716f with description of existing statuses. It's updated for the latest CI running

✅ Click here to open a full report in a separate page

Successful checks
Check nameDescriptionStatus
AST fuzzerRuns randomly generated queries to catch program errors. The build type is optionally given in parenthesis. If it fails, ask a maintainer for help✅ success
BuildsThere's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS✅ success
BuzzHouse (asan)There's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS✅ success
BuzzHouse (debug)There's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS✅ success
BuzzHouse (msan)There's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS✅ success
BuzzHouse (tsan)There's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS✅ success
BuzzHouse (ubsan)There's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS✅ success
ClickBenchRuns ClickBench with instant-attach table✅ success
Compatibility checkChecks that clickhouse binary runs on distributions with old libc versions. If it fails, ask a maintainer for help✅ success
Docker keeper imageThe check to build and optionally push the mentioned image to docker hub✅ success
Docker server imageThe check to build and optionally push the mentioned image to docker hub✅ success
Docs checkBuilds and tests the documentation✅ success
Fast testNormally this is the first check that is ran for a PR. It builds ClickHouse and runs most of stateless functional tests, omitting some. If it fails, further checks are not started until it is fixed. Look at the report to see which tests fail, then reproduce the failure locally as described here✅ success
Install packagesChecks that the built packages are installable in a clear environment✅ success
Integration testsThe integration tests report. In parenthesis the package type is given, and in square brackets are the optional part/total tests✅ success
Performance ComparisonMeasure changes in query performance. The performance test report is described in detail here. In square brackets are the optional part/total tests✅ success
Stateless testsRuns stateless functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc✅ success
Stress testRuns stateless functional tests concurrently from several clients to detect concurrency-related errors✅ success
Style checkRuns a set of checks to keep the code style clean. If some of tests failed, see the related log from the report✅ success
Unit testsRuns the unit tests for different release types✅ success
Upgrade checkRuns stress tests on server version from last release and then tries to upgrade it to the version from the PR. It checks if the new server can successfully startup without any errors, crashes or sanitizer asserts✅ success

@antonio2368 antonio2368 self-assigned this Nov 11, 2024
* 41 bits - 0.001%
)", 0) \
DECLARE(UInt64, output_format_parquet_bloom_filter_flush_threshold_bytes, 128 * 1024 * 1024, R"(
Where in the parquet file to place the bloom filters. If 0, each row group's bloom filters are written immediately after the row group. If very big, bloom filters for all row groups are written together near the end of the file. If something in the middle, bloom filters are written in groups of about this size.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

very big, something in the middle is really not clear, I would prefer:

Suggested change
Where in the parquet file to place the bloom filters. If 0, each row group's bloom filters are written immediately after the row group. If very big, bloom filters for all row groups are written together near the end of the file. If something in the middle, bloom filters are written in groups of about this size.
Where in the parquet file to place the bloom filters. If 0, each row group's bloom filters are written immediately after the row group. Otherwise, bloom filters are written in groups of about this size.

@al13n321
Copy link
Copy Markdown
Member Author

al13n321 commented Dec 5, 2024

https://s3.amazonaws.com/clickhouse-test-reports/71681/d541dbf40da39bd0686d675fc531dc7630c54a38/stateless_tests__release_.html seems to say that parquet encoding thread got stuck forever, but there's no stack trace (#72819), and I couldn't reproduce it after running the test ~1000 times using the binary from CI :(

@al13n321
Copy link
Copy Markdown
Member Author

al13n321 commented Dec 6, 2024

The test failure looks unrelated: #72817

@alexey-milovidov alexey-milovidov mentioned this pull request Dec 31, 2024
76 tasks
@clickhouse-gh
Copy link
Copy Markdown
Contributor

clickhouse-gh bot commented Jan 28, 2025

Dear @antonio2368, this PR hasn't been updated for a while. You will be unassigned. Will you continue working on it? If so, please feel free to reassign yourself.

@al13n321 al13n321 added this pull request to the merge queue Feb 7, 2025
Merged via the queue into master with commit 5ee1c43 Feb 7, 2025
114 checks passed
@al13n321 al13n321 deleted the bff branch February 7, 2025 05:49
@robot-clickhouse-ci-1 robot-clickhouse-ci-1 added the pr-synced-to-cloud The PR is synced to the cloud repo label Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr-not-for-changelog This PR should not be mentioned in the changelog pr-synced-to-cloud The PR is synced to the cloud repo

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants