Update submodule

[yi-xmu]

Summary by CodeRabbit

• Chores
  • Updated internal dependency reference for improved code organization.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The submodule reference for src/mongo/db/modules/eloq/data_substrate is updated to point to commit ca396ca35fd5fb04088886de01958a08d97e58a9, advancing the tracked version. No functional code changes are introduced.

Changes

Cohort / File(s)	Summary
Submodule Reference Update src/mongo/db/modules/eloq/data_substrate	Submodule commit pointer advanced from 6c17e4da... to ca396ca3...

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• update submodule: fix for tx operation retry #399: Also updates the submodule pointer for src/mongo/db/modules/eloq/data_substrate with the main PR advancing beyond the commit in that PR
• update subm #381: Updates the same submodule pointer to a different target commit
• update submoulde #375: Updates the same submodule reference with no functional code changes

Suggested labels

trigger-ci

Suggested reviewers

• liunyl
• lzxddz

Poem

🐰 A submodule hops to a newer hash,
CA396CA marches in with a dash,
No code broke, just pointers aligned,
The substrate strengthens, improved by design!

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Update submodule' is vague and does not specify which submodule or why it's being updated. While it accurately describes the action taken, it lacks the specificity to help teammates understand the purpose or impact of the change.	Consider using a more specific title such as 'Update data_substrate submodule to ca396ca3' or 'Update eloq/data_substrate submodule commit reference' to clarify which submodule is being updated and provide context about the update.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update_submodule_ysw

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 331d3f2 and 3d94a53.

📒 Files selected for processing (1)

• src/mongo/db/modules/eloq/data_substrate

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: githubzilla
Repo: eloqdata/eloqdoc PR: 279
File: src/mongo/db/modules/eloq/CMakeLists.txt:54-55
Timestamp: 2025-11-28T10:55:21.020Z
Learning: In src/mongo/db/modules/eloq/CMakeLists.txt, the CMake options EXT_TX_PROC_ENABLED, FORK_HM_PROCESS, and STATISTICS are used by the data_substrate submodule build system and should be retained as configuration interface options.

📚 Learning: 2025-11-28T10:55:21.020Z

Learnt from: githubzilla
Repo: eloqdata/eloqdoc PR: 279
File: src/mongo/db/modules/eloq/CMakeLists.txt:54-55
Timestamp: 2025-11-28T10:55:21.020Z
Learning: In src/mongo/db/modules/eloq/CMakeLists.txt, the CMake options EXT_TX_PROC_ENABLED, FORK_HM_PROCESS, and STATISTICS are used by the data_substrate submodule build system and should be retained as configuration interface options.

Applied to files:

• src/mongo/db/modules/eloq/data_substrate

🔇 Additional comments (1)

src/mongo/db/modules/eloq/data_substrate (1)

1-1: No action required. The submodule update is a straightforward commit reference change. The CMake configuration options (EXT_TX_PROC_ENABLED, FORK_HM_PROCESS, STATISTICS) are already present in src/mongo/db/modules/eloq/CMakeLists.txt and will remain intact.

---

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.}