July 06, 2025: This Week in OpenDAL

["github-actions[bot] (via GitHub)" <gi...@apache.org>]

GitHub user github-actions[bot] created a discussion: July 06, 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 past week has been vibrant with contributions ranging from refactoring efforts, dependency updates, and feature implementations to discussions on improving service conventions and metadata handling. Key progress has been made in migrating services to the `Access` API, enhancing bindings, and addressing bugs.

## Key Ongoing Projects
- **Migration to Access API**:
  - #6344 by @meteorgan refactors the `dashmap` service to implement `Access` directly, part of the broader migration effort tracked in #5739.
  - #6328 by @NoxTav migrates the SQLite service from `adapter::kv` to `Access`.

- **Node.js Bindings Enhancements**:
  - #6349 by @kingsword09 adds `DeleteOptions` support for the new options API, aligning with RFC-6213.
  - #6322 and #6320 by @kingsword09 introduce `WriteOptions` and `ListOptions` support, enabling more granular operations.

- **Performance Benchmarking**:
  - #6341 by @yuchanns introduces benchmarks comparing OpenDAL's Go bindings against the AWS S3 SDK.

- **Cache Layer Design**:
  - #6297 by @koushiro proposes a new Cache Layer RFC, aiming to improve caching capabilities across services.

## Priority Items
- **Refactoring Services**:
  - #6344 by @meteorgan and #6328 by @NoxTav need thorough review and testing to ensure a smooth transition to the `Access` API.

- **Node.js Bindings**:
  - #6349, #6322, and #6320 by @kingsword09 require validation to ensure compatibility with the new options API.

- **Bug Fixes**:
  - #6326 by @kingsword09 addresses the `if_not_exists` flag issue in the filesystem service.
  - #6327 by @kingsword09 resolves issues with `tmp_path` generation for append operations across multiple services.

## Notable Discussions
- **Reducing Dependabot Traffic**:
  - #6364 by @erickguan proposes reducing Dependabot update frequency and grouping dependencies to minimize PR traffic and improve maintainability.

- **Metadata Handling**:
  - #6346 by @sunng87 highlights an issue where DigitalOcean Space users are blocked by AWS metadata access, sparking discussions on improving fallback mechanisms.

- **Service Conventions**:
  - #5702 continues to track the refactoring of services to adopt `backend.rs` and `core.rs` conventions, improving maintainability and readability.

## Emerging Trends
- **Standardization**:
  - A strong push towards refactoring services to adopt standardized APIs and conventions, as seen in the migration to the `Access` API.

- **Cross-Language Parity**:
  - Efforts to align capabilities across bindings (e.g., Node.js and Go) are gaining traction.

- **Performance Optimization**:
  - Benchmarking and memory optimization are becoming central themes, as evidenced by #6341.

## Good First Issues
- **Enable Features in C++ Bindings**:
  - #6250: Introduce user-configurable feature flags for C++ bindings. Requires basic knowledge of C++ and OpenDAL's architecture.

- **Publish Source and Lock Files for Binaries**:
  - #6198: Facilitate packaging for NixOS by publishing source code and lock files for binaries like `oli` and `oay`.

- **Refactor Services**:
  - #5702: Migrate services to use `backend.rs` and `core.rs` conventions. Ideal for contributors looking to understand service architecture.

- **Implement Write Returns Metadata**:
  - #5693: Extend metadata extraction for write operations across services. Suitable for contributors familiar with Rust and OpenDAL's metadata handling.

Thank you to all contributors for your efforts in advancing the project! 🚀

GitHub link: https://github.com/apache/opendal/discussions/6367

----
This is an automatically sent email for dev@opendal.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@opendal.apache.org