January 11, 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 has been bustling with activity over the past week, featuring contributions focused on new features, bug fixes, and enhancements across services, layers, and bindings. Notable efforts include improvements to caching layers, OneDrive service fixes, and modularization of the codebase. Discussions around new features and debugging workflows have also been active.

Key Ongoing Projects

• CacheLayer Implementation (feat(layers): implement CacheLayer #7108 by @koushiro): Progress continues on implementing the CacheLayer, a key feature to enhance caching capabilities in OpenDAL. This is part of the broader RFC-6297 initiative.
• Foyer Layer Development (feat: introduce foyer layer #6366 by @MrCroxx): Work is ongoing to introduce the FoyerLayer for hybrid cache integration. This is part of the RFC-6370 initiative, with related discussions in Tracking issues for RFC-6370: Foyer Layer #6372.
• Onedrive Service Fixes (fix(onedrive): correctly handle root directory listing #7114 by @Somsubhra-Nandi): Fixes are being implemented to address root directory listing issues in the OneDrive service, resolving bug: Onedrive service list("/") returns empty result due to incorrect URL construction #7102.
• Java Bindings Enhancements (feat: add additional layers support #7128 by @Retrospection): Additional layers are being added to the Java bindings to align them with the Python and Node.js bindings.
• Route Layer Implementation (feat(layers/route): impl route layer as rfc 7130 #7137 by @PsiACE): A new RouteLayer is being developed to enable path-based request routing, as proposed in RFC-7130 (RFC-7130: Route Layer #7130).

Priority Items

• fix(onedrive): correctly handle root directory listing #7114 by @Somsubhra-Nandi: Fixes the OneDrive root directory listing issue (bug: Onedrive service list("/") returns empty result due to incorrect URL construction #7102). This PR is critical and requires review and testing.
• feat(layers): implement CacheLayer #7108 by @koushiro: The CacheLayer implementation is a significant addition and needs further review and contributions.
• Tracking issues for RFC-6370: Foyer Layer #6372 by @Xuanwo: The FoyerLayer tracking issue for hybrid cache integration is a high-priority initiative that requires community input and contributions.

Notable Discussions

• Seek implementation has unexpected behaviour #7113 by @ilsley: Discussion on unexpected behavior in the Seek implementation for Buffer and how it can be improved for better alignment with standard expectations.
• new feature: Relax stat to properly differentiate between directory and file #6761 by @chitralverma: Proposal to relax the stat method for differentiating between directories and files without requiring explicit path formats.
• feature request: support password login for sftp service #2966 by @silver-ymz: Ongoing discussion about adding password login support for the SFTP service, which is currently blocked by an upstream issue in the OpenSSH Rust library.

Emerging Trends

• Modularization of Codebase: A significant effort is underway to split services and layers into separate crates, improving maintainability and scalability.
• Focus on Layers: Development of new layers like CacheLayer and RouteLayer highlights the growing emphasis on enhancing modularity and functionality.
• WASM Support Expansion: The community is actively working on expanding support for the wasm32-unknown-unknown target, with progress on multiple services and discussions around testing and benchmarking.

Good First Issues

• Tracking issues for RFC-6828: Core #6829: Tracking issues for RFC-6828: Core
  This involves splitting services and layers into their own crates, providing a great opportunity for new contributors to learn about Rust's module system and OpenDAL's architecture.

• Implement Write Returns Metadata for all services #5693: Implement Write Returns Metadata for all services
  Contributors can help extend the Write Returns Metadata feature to various services. This task involves extracting metadata from write responses and is a straightforward entry point for new contributors.

• Tracking issues of RFC: Object Versioning #2611: Tracking issues of RFC: Object Versioning
  Help implement object versioning for services like azblob, gcs, and onedrive. This is a well-scoped task with clear guidelines and documentation.

• Tracking issues of RFC-5479: Context #5480: Tracking issues of RFC-5479: Context
  This issue tracks the implementation of the Context feature. It's a good entry point for contributors interested in core functionality.

• Tracking issues of OpenDAL wasm32-unknown-unknown target support #3803: Tracking issues of OpenDAL wasm32-unknown-unknown Target Support
  Join the effort to expand OpenDAL's support for the wasm32-unknown-unknown target. Tasks include adding support for more services and integrating behavior tests.