GitHub user github-actions[bot] created a discussion: August 24, 2025: This Week in OpenDAL
*This weekly update is generated by LLMs. You're welcome to join our [Discord](https://opendal.apache.org/discord/) for in-depth discussions.* ## Overall Activity Summary The `apache/opendal` repository has seen significant activity this week, with a focus on enhancing backend services (e.g., S3, GCS, Azure Blob), improving CI workflows, and adding new features like security token support for Aliyun OSS. Contributors have also worked on refactoring, bug fixes, and expanding language bindings, particularly for C++ and Python. ## Key Ongoing Projects - **Aliyun OSS Enhancements** - #6530 by @jackye1995 adds missing Azure authentication features, including OAuth, bearer tokens, and managed identity support. - #6511 by @cavivie introduces support for security tokens in Aliyun OSS, improving access control flexibility. - **S3 Service Improvements** - #6532 by @jackye1995 adds S3 tagging write support, enabling users to write object tags with enhanced compatibility. - #6524 by @jackye1995 introduces configuration aliases for better compatibility with Apache Arrow's object_store. - **GCS Service Enhancements** - #6529 by @jackye1995 implements comprehensive HTTP client configuration features for GCS, providing feature parity with object_store. - #6526 by @jackye1995 adds configuration aliases for better Arrow object_store compatibility. - **CI Pipeline Modernization** - #6435 by @kingsword09 migrates CI images for etcd, memcached, and Redis to new sources, addressing Bitnami's upcoming restrictions on free image access. - **C++ Binding Improvements** - #6460 by @devillove084 makes the C++ binding build more robust, paving the way for better support for asynchronous features. ## Priority Items - **Critical Features Awaiting Review** - #6532 by @jackye1995 (S3 tagging support) and #6529 by @jackye1995 (GCS HTTP client configuration) are key features that need prompt review to enhance backend capabilities. - #6524 by @jackye1995 (S3 configuration aliases) is crucial for improving compatibility with Apache Arrow's object_store. - **Bug Fixes** - #6521 by @leiysky addresses a critical bug where write operations fail to split payloads into chunks as configured. - **Pending Refactor** - #6313 by @Xuanwo removes `stat_has_xxx` and `list_has_xxx` capabilities, requiring downstream projects to adapt. ## Notable Discussions - **Replacement for Removed Capabilities** - #6522: @killme2008 raised concerns about the removal of `list_has_content_length` and similar capabilities, seeking guidance on alternatives. - **GitHub Models for Weekly Summaries** - #6519: @kingsword09 proposed migrating the weekly summary generation from OpenAI to GitHub Models for better integration and security. ## Emerging Trends - **Backend Configurability**: Multiple PRs (e.g., #6532, #6529, #6524) focus on enhancing backend configurability, reflecting a trend toward user-centric storage solutions. - **CI Sustainability**: Efforts like #6435 highlight the community's focus on long-term CI stability and compatibility with external dependencies. - **Language Binding Expansion**: Updates to C++ (#6460) and Python (#6518) bindings indicate a push to make OpenDAL accessible across diverse programming ecosystems. ## Good First Issues - #4975: Add support for assume-role tags in S3. This is a great way to get familiar with S3 backend configuration. - #5693: Implement Write Returns Metadata for all services. Start with simpler services like `fs` to extend metadata extraction. - #6198: Publish source and lock files for binaries. Ideal for contributors interested in improving build and release processes. - #5702: Refactor services to use the `backend.rs` and `core.rs` convention. A good entry point for contributors looking to improve code organization. - #5480: Refactor services to adopt the new `Context` convention. This task is approachable and helps improve consistency across the codebase. GitHub link: https://github.com/apache/opendal/discussions/6533 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
