Avoid forcing checkpoint flush when data sync memory quota is full

[thweetkomputer]

Summary by CodeRabbit

• Chores
  • Internal code formatting and organizational adjustments to preprocessor configurations with no impact on functionality or end-user features.
  • Updated internal dependency references.

[coderabbitai]

Walkthrough

The PR adjusts preprocessor conditional formatting in ha_eloq.cc by realigning line breaks and consolidating related conditions for improved readability. Additionally, the tx_service submodule pointer is updated to a newer commit. No functional or runtime behavior changes are introduced.

Changes

Cohort / File(s)	Change Summary
Preprocessor formatting adjustments storage/eloq/ha_eloq.cc	Reflow OR-conditions in #if blocks (ELOQDS_RKDB_CLOUD, LOG_STATE_TYPE_RKDB_CLOUD, LOG_STATE_TYPE_RKDB_ALL), merge line continuations for AWS/DynamoDB/RKDB/S3 related guards, consolidate conditional compilation checks in eloq_done_func, remove stray blank line. No logic changes.
Submodule pointer update storage/eloq/tx_service	Submodule pointer updated from commit b823488d3c6e01e1bb2e11a4469e2823ba0be9a6 to c689ba46cd96d232240e2fe8b7b118fd01ddc0f5.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• #122: Updates the storage/eloq/tx_service submodule pointer to a newer commit.
• #133: Updates the storage/eloq/tx_service submodule pointer (metadata change).

Suggested reviewers

• liunyl

Poem

🐰 With lines so neat and guards aligned,
The preprocessor's thoughts are now refined!
And tx_service hops to version new,
A tidy patch—just right on cue! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title Check	⚠️ Warning	The pull request title "Avoid forcing checkpoint flush when data sync memory quota is full" suggests functional changes to checkpoint flushing logic and memory quota handling behavior. However, the actual changeset consists solely of formatting adjustments to preprocessor conditionals and whitespace in storage/eloq/ha_eloq.cc, along with a submodule pointer update to storage/eloq/tx_service. The AI-generated summary explicitly confirms "no semantic changes to control flow or runtime behavior" and "only formatting/line-structure changes in preprocessor guards." The title does not accurately represent the actual changes, making it misleading about what the PR accomplishes.	The title should be updated to reflect the actual changes in the PR. A more accurate title might be something like "Refactor preprocessor conditionals formatting in ha_eloq.cc and update tx_service submodule" or similar, which would correctly describe the formatting adjustments and submodule update rather than implying functional changes to checkpoint flushing behavior that are not present in the changeset.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 42c52db and b504001.

📒 Files selected for processing (2)

• storage/eloq/ha_eloq.cc (4 hunks)
• storage/eloq/tx_service (1 hunks)

🔇 Additional comments (1)

storage/eloq/tx_service (1)

1-1: The submodule update contains a different fix than stated in the PR objective.

The commit c689ba46cd96d232240e2fe8b7b118fd01ddc0f5 in the tx_service submodule is a bug fix for "incorrect initialization of mv_base_idx_vec_ in constructor of txservice::HashPartitionDataSyncScanCc" with formatting adjustments to snapshot_manager.cpp. This fix addresses data sync scanning behavior, not checkpoint flushing logic.

There is a misalignment between the PR objective stated in the review comment ("avoid forcing checkpoint flush when data sync memory quota is full") and the actual contents of this submodule update. Verify that the correct submodule commit was intended for this PR, or clarify if the PR description should be updated to reflect the actual fix being deployed.

Likely an incorrect or invalid review comment.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}