Update submodule for update datasyncscan execution

[yi-xmu]

Summary by CodeRabbit

• Chores
  • Updated an internal submodule pointer to a newer commit as part of routine maintenance. No user-visible functional or behavioral changes; low risk.

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

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Update git submodule pointer for src/mongo/db/modules/eloq/data_substrate from commit 755c4b7fb98a1411cbe0abde27bab32ffe10a54c to 42f15b931cdadd2a19bd0e0ff3eff6da40dd2ebf. No in-repo code changes or behavioral modifications.

Changes

Cohort / File(s)	Summary
Submodule update src/mongo/db/modules/eloq/data_substrate	Advance git submodule reference from 755c4b7fb98a1411cbe0abde27bab32ffe10a54c → 42f15b931cdadd2a19bd0e0ff3eff6da40dd2ebf. Repository pointer change only; no files edited in-tree.

Sequence Diagram(s)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• update submodule #318: Also updates src/mongo/db/modules/eloq/data_substrate submodule pointer (no functional changes).
• update subm #386: Updates the same submodule pointer to a different commit.
• update subm #381: Similar submodule pointer-only update for the same path.

Suggested reviewers

• liunyl
• lzxddz
• xiexiaoy

Poem

🐇 I nudged a hash beneath the log-tree air,
A tiny hop — a pointer changed with care.
No code awakened, tests still hum the tune,
Just a quiet shift beneath the moon. ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly indicates the main change: updating a submodule related to datasyncscan execution, which matches the raw summary showing a submodule pointer update in the eloq/data_substrate module.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 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 5bc361f and be6f9c6.

📒 Files selected for processing (1)

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

---

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e8c34ce and b22ab65.

📒 Files selected for processing (1)

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

🧰 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

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Provide details on the data_substrate submodule update and verify testing.

Submodule updates affecting core infrastructure require documentation of changes and verification of compatibility:

• Specify what changes are included in this submodule update, particularly improvements to "datasyncscan execution"
• Confirm testing was performed with the new submodule version
• Verify the new submodule maintains compatibility with the existing CMake build configuration, including the documented options (EXT_TX_PROC_ENABLED, STATISTICS, etc.)
• Note any new dependencies or API changes that could affect downstream consumers