May 18, 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 seen robust activity over the past week, with contributions focused on enhancing service capabilities, addressing bugs, and refining APIs for better usability. Notable efforts include the implementation of new features, refactoring for code maintainability, and discussions around improving blocking API support. Contributors have actively engaged in discussions and submitted PRs, showcasing a vibrant and collaborative community.

---

Key Ongoing Projects

• Blocking API Refactor:

  • RFC-6189: Remove Native Blocking #6189 by @Xuanwo introduces an RFC to remove native blocking API support, aiming to simplify code maintenance and accelerate development.
  • Related discussion: Remove blocking API entirely.

• Multi-table Access for Redb:

  • feat(core): support sharing one redb database between different Operators #6173 by @TD-Sky enables sharing one Redb database across different operators, addressing multi-table access needs.

• Streaming Reader/Writer for Python Bindings:

  • feat(bindings/python): Enhance Reader and Writer #6086 by @chitralverma enhances Python bindings with streaming capabilities, allowing users to handle large datasets efficiently.

• CLI Enhancements:

  • feat(bin/oli): support cp to dir #6140 by @asukaminato0721 adds support for copying files to directories in the oli CLI tool, improving usability.

---

Priority Items

• Open PRs Needing Review:

  • feat: initial Operator::from_uri implementation #5482 by @jorgehermo9: Implements Operator::from_uri. Contributor seeks feedback on test placement and API alignment.
  • feat(core): capability list for redb #6165 by @TD-Sky: Adds list capability for Redb. This PR introduces significant changes and requires review for correctness.

• Critical Bugs:

  • Bindings D CI has been disabled #6010: Bindings D CI has been disabled due to upstream issues. Requires resolution to restore CI functionality.
  • bug: bindings/java: Exception in thread "main" java.lang.UnsatisfiedLinkError: /tmp/libopendal_java16119350451049595665.so: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.39' not found #6080: Java binding fails due to GLIBC version mismatch. This impacts compatibility and needs attention.

---

Notable Discussions

• Remove blocking API entirely from `raw::Access` #6126: Remove Blocking API Entirely:

  • Led by @Xuanwo, this discussion explores removing blocking API from raw::Access to reduce code duplication and simplify development.

• Clarification on BlockingOperator and its operations #6188: Clarification on BlockingOperator:

  • @chitralverma raises questions about the separation of blocking and async APIs, sparking valuable insights into design decisions.

• [VOTE] Release Apache OpenDAL 0.53.3 - Vote Round 1 #6187: Release Apache OpenDAL 0.53.3:

  • A vote is underway for the next release, focusing on bug fixes and feature enhancements.

---

Emerging Trends

1. Refactoring for Maintainability:

   • Several PRs focus on restructuring code for better readability and maintainability, such as dev: extract service config structs' identifier #6170 and refactor(bindings/java): deprecate append in favor of write with append=true #6169.

2. Enhanced Service Capabilities:

   • Contributors are actively adding new features to existing services, such as list support for Redb (feat(core): capability list for redb #6165) and metadata extraction (feat(services/azblob): implement write returns metadata #5958).

3. Focus on Multi-language Bindings:

   • Efforts to improve bindings across languages (Python, Java, Go) highlight the project's commitment to accessibility.

---

Good First Issues

• Tracking issue: Refactor services to use the backend.rs and core.rs convention #5702: Refactor Services to Use backend.rs and core.rs Convention:

  • This task involves reorganizing service code for consistency. Ideal for contributors looking to understand service architecture.

• Implement Write Returns Metadata for all services #5693: Implement Write Returns Metadata for All Services:

  • Contributors can help extend metadata extraction logic to additional services. A straightforward task with clear guidelines.

• Tracking issues of RFC-5479: Context #5480: Tracking Issues of RFC-5479 (Context):

  • Implement context-related features across services. A good entry point for understanding OpenDAL's core abstractions.

• Tracking issues of user metadata support #4842: User Metadata Support:

  • Add support for user-defined metadata in various services. This task is approachable and impactful.

---

Thank you to all contributors for your efforts this week! Let’s keep the momentum going. 🚀