chore:add direct_io_buffer_pool_size parsing

[thweetkomputer]

Here are some reminders before you submit the pull request

• Add tests for the change
• Document changes
• Reference the link of issue using fixes eloqdb/tx_service#issue_id
• Reference the link of RFC if exists
• Pass ./mtr --suite=mono_main,mono_multi,mono_basic

Summary by CodeRabbit

• New Features
  • Added command-line flag configuration for EloqStore DirectIO buffer pool size per shard. The flag takes precedence over configuration file values when explicitly specified.

[coderabbitai]

Walkthrough

A new command-line configuration flag eloq_store_direct_io_buffer_pool_size (default 16) is added to enable runtime override of the EloqStore DirectIO buffer pool size, with precedence handling applied during EloqStoreConfig initialization.

Changes

Cohort / File(s)	Summary
Configuration Flag Addition store_handler/eloq_data_store_service/eloq_store_config.cpp	Added new DEFINE_uint32 flag for DirectIO buffer pool size and updated EloqStoreConfig constructor to initialize the corresponding field using the flag value when non-default, otherwise falling back to config file value.
Submodule Update store_handler/eloq_data_store_service/eloqstore	Submodule commit hash updated; no code-level behavioral changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• chore: update submodule eloqstore and add new parameters to eloq_store_config #370: Adds similar DEFINE_uint32 flags and initializes corresponding fields in the same file and constructor.
• feat: adapt to eloqstore memory upload and add eloq_store_max_write_concurrency parameters #407: Modifies the same file and EloqStoreConfig constructor to add/initialize new configuration flags.
• eloqstore: remove write limit #375: Updates EloqStoreConfig initialization in the same file for related configuration field management.

Suggested reviewers

• liunyl
• lzxddz

Poem

🐰 A buffer pool flag hops into place,
With size sixteen, it sets the pace,
Command-line or config—take your pick,
Configuration precedence, swift and slick! ✨

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description contains only a checklist template with unchecked items and no descriptive content explaining the change, its rationale, or implementation details.	Provide substantive description of the change: explain what direct_io_buffer_pool_size does, why it's configurable, and briefly describe the implementation.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore:add direct_io_buffer_pool_size parsing' accurately describes the main change, which is adding a new configuration flag for parsing direct_io_buffer_pool_size in EloqStore.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore-io-buffer-zc

---

No actionable comments were generated in the recent review. 🎉

---

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