You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 seen significant activity this week, with a focus on refactoring services and layers into separate crates as part of the RFC-6828 core split initiative. Contributors have also worked on new features, bug fixes, and performance improvements across multiple areas, including bindings, caching layers, and service-specific enhancements. Discussions around upcoming releases and cross-language FFI integration have also gained traction.
Cross-language FFI Integration (Cross-language FFI #7103): @gatesn initiated a discussion on enabling OpenDAL clients configured in Python to be passed to Rust libraries using PyO3, fostering interoperability.
Refactoring Focus: The ongoing core split initiative is driving a major restructuring of the repository, with services and layers being moved into standalone crates for better modularity.
Increased Collaboration: Contributors are actively engaging in discussions and collaborating across issues and pull requests, reflecting a vibrant and growing community.
Performance Optimization: Several PRs focused on improving performance, particularly in bindings and layer implementations.
Good First Issues
Tracking issues for RFC-6828: Core #6829: Tracking issues for RFC-6828 (Core Split Initiative). This issue provides detailed steps for splitting services and layers into standalone crates, making it an excellent entry point for new contributors.
Implement Write Returns Metadata for all services #5693: Implement Write Returns Metadata for all services. Contributors can help extend this feature to services like Azfile, B2, and GDrive by extracting relevant metadata from write responses.
Tracking issues of RFC-5479: Context #5480: Tracking issues of RFC-5479 (Context). This issue focuses on migrating OpenDAL to a context-based approach, with tasks available for various layers.
We encourage new contributors to explore these issues and join the OpenDAL community to make an impact!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
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 seen significant activity this week, with a focus on refactoring services and layers into separate crates as part of the RFC-6828 core split initiative. Contributors have also worked on new features, bug fixes, and performance improvements across multiple areas, including bindings, caching layers, and service-specific enhancements. Discussions around upcoming releases and cross-language FFI integration have also gained traction.
Key Ongoing Projects
Core Split Initiative:
Cache Layer Development:
Performance Enhancements:
OperatorInputStream(feat(bindings/java): Speed up the performance ofOperatorInputStream#7088) by @Xuanwo, with follow-up fine-tuning in chore: fine tune OperatorInputStream #7089 by @tisonkun.New Features:
HotpathLayerwas introduced (feat(layers/hotpath): add HotpathLayer integration #7083) by @PsiACE, enabling profiling of operations with the hotpath crate.Priority Items
Open Pull Requests:
PermissionDeniederrors. Requires testing and validation.CompleteWriterfor enforcing invariants. Needs further review.Critical Issues:
list("/")returns empty result due to incorrect URL construction #7102 by @fadflka: Bug in OneDrive service wherelist("/")returns an empty result due to incorrect URL construction.PermissionDeniederrors, impacting usability.Notable Discussions
Emerging Trends
Good First Issues
Write Returns Metadatafor all services #5693: ImplementWrite Returns Metadatafor all services. Contributors can help extend this feature to services like Azfile, B2, and GDrive by extracting relevant metadata from write responses.We encourage new contributors to explore these issues and join the OpenDAL community to make an impact!
Beta Was this translation helpful? Give feedback.
All reactions