enable parallel view processing for inserts

[iuwqyir]

TL;DR

Enable parallel view processing in ClickHouse connection settings.

What changed?

Added the parallel_view_processing setting with a value of "1" to the ClickHouse connection settings in the connectDB function.

How to test?

1. Deploy the updated code to a test environment
2. Verify that ClickHouse queries involving views execute properly
3. Monitor query performance to ensure parallel view processing is working as expected

Why make this change?

Enabling parallel view processing allows ClickHouse to process views more efficiently by executing parts of view queries in parallel. This can significantly improve performance for complex queries that involve views, especially on systems with multiple CPU cores.

Summary by CodeRabbit

• Chores
  • Updated database connection settings to include an additional ClickHouse configuration for improved processing. No user-facing changes.

[coderabbitai]

Walkthrough

A new ClickHouse connection setting, "parallel_view_processing": "1", was added to the settings map in the connectDB function. This change augments the set of options used when establishing a database connection. No other logic or exported entities were modified.

Changes

File(s)	Change Summary
internal/storage/clickhouse.go	Added "parallel_view_processing": "1" to connection settings in connectDB.

Sequence Diagram(s)

sequenceDiagram
    participant App
    participant ClickHouse

    App->>ClickHouse: Connect with settings (including "parallel_view_processing": "1")
    ClickHouse-->>App: Connection established

Loading

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[iuwqyir]

• enable parallel view processing for inserts #220 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

internal/storage/clickhouse.go (1)

103-107:

❓ Verification inconclusive

Add context and verify compatibility for the new setting
You’ve enabled parallel_view_processing = "1" to allow view queries to execute parts in parallel. To ensure smooth rollout:

1. Document why this setting is required, link to ClickHouse docs, and note the minimum CH server version (e.g., 22.6+) that supports it.
2. Confirm that all environments (dev/test/prod) run a ClickHouse version which recognizes this setting; otherwise it may be ignored or rejected.

Please confirm server compatibility—e.g., via:

and add a comment or README entry referencing the setting’s support matrix.

---

🏁 Script executed:

clickhouse-client --query "SELECT version();"

Length of output: 155

---

Verify ClickHouse version compatibility
We attempted to run clickhouse-client --query "SELECT version();" in this environment, but the binary isn’t available. Please manually confirm that all environments (dev/test/prod) are running a ClickHouse server version that supports parallel_view_processing (e.g., ≥22.6). Once confirmed, add or update documentation to:

• Explain why parallel_view_processing = "1" is required.
• Link to the official ClickHouse docs on this setting.
• Note the minimum server version needed.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 23cc670 and fce6a34.

📒 Files selected for processing (1)

• internal/storage/clickhouse.go (1 hunks)