September 14, 2025: This Week in OpenDAL

[github-actions[bot]]

This weekly update is generated by LLMs. You're welcome to join our Discord for in-depth discussions.

Overall Activity Summary

The apache/opendal repository has experienced steady activity over the past week, with contributions spanning backend service enhancements, refactoring efforts, CI pipeline improvements, and language binding expansions. Several PRs were merged, while others remain under active review. Discussions around release planning and roadmap goals have also been vibrant, showcasing a collaborative and forward-looking community.

Key Ongoing Projects

• Backend Service Enhancements:

  • refactor: Migrate sqlite from adapter::kv to Access instead #6328 by @NoxTav refactors SQLite integration by migrating from adapter::kv to Access.
  • feat(services/oss): allow users to specify endpoint addressing style #6504 by @howardlau1999 introduces endpoint addressing style options for OSS, improving user configurability.
  • fix(bindings/d): Enhance D bindings build script and tests for OpenDAL #6569 by @kingsword09 enhances D bindings build scripts and tests, addressing CI failures.

• Language Binding Expansion:

  • fix(services/obs): send Range header only for non-full reads #6574 by @QuakeWang fixes OBS read requests to align with HTTP semantics, improving compatibility.
  • chore(core): typo: update comments on BytesRange::new #6570 by @TheR1sing3un updates comments in BytesRange::new, ensuring clarity in the codebase.

• CI Pipeline Modernization:

  • ci: Switch from --nocapture to --no-capture #6567 by @kingsword09 updates CI workflows to use the new --no-capture flag, ensuring compatibility with Rust 1.88.

Priority Items

• Critical PRs:

  • refactor: Migrate sqlite from adapter::kv to Access instead #6328 by @NoxTav requires review as it introduces significant refactoring for SQLite integration.
  • feat(services/oss): allow users to specify endpoint addressing style #6504 by @howardlau1999 enhances OSS configurability, which is critical for user flexibility.

• Bug Fixes:

  • fix(services/obs): send Range header only for non-full reads #6574 by @QuakeWang resolves incorrect OBS Range header behavior, improving service reliability.

• Release Planning:

  • Tracking issues of OpenDAL v0.54.1 Release #6557 by @Xuanwo tracks tasks for the upcoming v0.54.1 release and requires community input.

Notable Discussions

• v0.54.1 #6573: Discussion around v0.54.1 release planning, highlighting new features and fixes.
• [RESULT][VOTE] Release Apache OpenDAL v0.54.1 - Vote Round 1 #6572: Announcement of successful voting for Apache OpenDAL v0.54.1 release.
• HTTP operator with custom certificate in python bindings #6418: @bennyz raised a question about using custom certificates in Python bindings for HTTP operators, prompting technical insights from the community.

Emerging Trends

• Backend Configurability: Multiple PRs focus on enhancing backend service configurability, reflecting a user-centric approach to storage solutions.
• Language Binding Expansion: Updates to Ruby, Python, and D bindings indicate efforts to make OpenDAL accessible across diverse programming ecosystems.
• CI Sustainability: Migration of CI workflows to newer standards ensures long-term compatibility and stability.

Good First Issues

• new feature: Allow s3 service to configure assume role's tags #4975: Allow S3 service to configure assume role's tags. This introduces contributors to S3 backend configuration and access control.
• Implement Write Returns Metadata for all services #5693: Implement Write Returns Metadata for all services. Contributors can start with simpler services like fs to extend metadata extraction.
• new feature: publish the source and lock files for binaries (oli, oay...) #6198: Publish the source and lock files for binaries. Ideal for contributors interested in improving build and release processes.
• Tracking issue: Refactor services to use the backend.rs and core.rs convention #5702: Refactor services to use the backend.rs and core.rs convention. A good entry point for contributors looking to improve code organization.
• Tracking issues of RFC-5479: Context #5480: Refactor services to adopt the new Context convention. This task is approachable and helps improve consistency across the codebase.