February 15, 2026: 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 experienced robust activity this week, with contributions spanning new features, bug fixes, and refactoring. Key areas of focus included enhancements to Azure Blob Storage, Python bindings, and the introduction of new APIs. Discussions around improving tail latency, object versioning, and AI usage guidelines also gained traction, reflecting the community's collaborative and forward-thinking approach.

Key Ongoing Projects

• Azure Blob Storage Enhancements:
  • RFC-7182: file restoration API #7182 by @NikitaMatskevich introduces an RFC for a file restoration API, laying the groundwork for restoring soft-deleted files.
  • new feature: Implement Volcengine Object Storage (TOS) Service Support #7152 by @ddupg proposes adding support for Volcengine Object Storage (TOS), expanding the range of supported services.
• Python Bindings Refactor:
  • refactor(bindings/python): Update Stubs and dependencies for split #7181 by @chitralverma refactors Python bindings, simplifying APIs and preparing for future reorganization.
• Metadata Improvements:
  • fix(services/fs): add content length and modified time to metadata #7188 by @matthambrecht addresses missing file size and modified time metadata for the services/fs lister, improving metadata accuracy.
• New Features:
  • feat(services/s3): Add a way to specify a default object ACL #7186 by @antoine-de adds support for specifying a default object ACL in the S3 service, enhancing configurability for object creation.

Priority Items

• Pull Requests Needing Review:
  • feat(hf): support writing and reading from both http and xet #7185 by @kszucs introduces support for reading and writing using the xet protocol, a significant enhancement for interoperability.
  • refactor(bindings/python): Update Stubs and dependencies for split #7181 by @chitralverma refactors Python bindings, which is critical for maintainability and future development.
  • fix(services/fs): add content length and modified time to metadata #7188 by @matthambrecht fixes metadata issues in the services/fs lister, addressing a key bug.
• Issues Requiring Attention:
  • new feature: hedged request support for read-only operations #7189 by @dentiny proposes adding hedged request support for read-only operations to reduce tail latency, a valuable feature for production environments.
  • new feature: Implement Volcengine Object Storage (TOS) Service Support #7152 by @ddupg focuses on implementing Volcengine Object Storage (TOS) support, which will broaden the project's capabilities.

Notable Discussions

• Object Versioning:
  • Tracking issues of RFC: Object Versioning #2611 by @suyanhanx tracks the implementation of object versioning across services, a critical feature for data safety and recovery.
• Hedged Requests for Tail Latency:
  • new feature: hedged request support for read-only operations #7189 by @dentiny discusses the feasibility of implementing hedged requests to improve performance for read-only operations.
• AI Usage Guidelines:
  • Set up AI usage guidelines #6795 by @Xuanwo proposes establishing guidelines for responsible AI usage in contributions, ensuring quality and maintainability.

Emerging Trends

• Focus on Azure Blob Storage: Several contributions, including RFC-7182: file restoration API #7182 and feat(services/azblob): implement list_with_deleted operation in azblob #7151, highlight ongoing efforts to enhance Azure Blob Storage support, particularly around soft-delete and restoration capabilities.
• Python Bindings Maturity: Refactoring efforts in refactor(bindings/python): Update Stubs and dependencies for split #7181 and related PRs indicate a push to improve Python bindings, making the project more accessible to Python developers.
• Tail Latency Optimization: Discussions like new feature: hedged request support for read-only operations #7189 reflect a growing interest in optimizing performance for latency-sensitive operations.

Good First Issues

• new feature: Allow s3 service to configure assume role's duration-seconds #4976: Allow S3 service to configure assume role's duration-seconds. This issue involves adding support for configuring the duration of assume role sessions in the S3 service. Ideal for contributors familiar with AWS and Rust.
• new feature: Allow s3 service to configure assume role's tags #4975: Allow S3 service to configure assume role's tags. Similar to new feature: Allow s3 service to configure assume role's duration-seconds #4976, this issue focuses on enabling tag configuration for assume roles in S3.
• Tracking issues for RFC-6828: Core #6829: Tracking issues for RFC-6828: Core. This involves splitting services and layers into separate crates, providing a great opportunity to understand the codebase structure.
• Implement Write Returns Metadata for all services #5693: Implement Write Returns Metadata for all services. Contributors can work on extracting metadata from write responses, a straightforward task with clear guidelines.
• Tracking issues of RFC: Object Versioning #2611: Tracking issues for RFC: Object Versioning. This involves implementing object versioning for various services, a critical feature for data safety and recovery.

New contributors are encouraged to tackle these approachable issues to get familiar with the project and make meaningful contributions.