build(deps): upgrade opendal to 0.46

[tisonkun]

I hereby agree to the terms of the GreptimeDB CLA.

Refer to a related PR or issue link (optional)

What's changed and what's your intention?

1. Upgrade OpenDAL to 0.46.
2. Upgrade reqwest to 0.12 cascading.

Checklist

• I have written the necessary rustdoc comments.
• I have added the necessary unit tests and integration tests.
• This PR requires documentation updates.

[Xuanwo]

Hi, in tisonkun#5, I make greptime buildable with opendal 0.46.

We still have more work to do moving forward. For example, we need to reconsider the use of AsyncRead + AsyncSeek in our codebase, as they are not suitable for object storage services and upcoming completion-based IO.

Also, since opendal 0.46, it returns Buffer which provide zero-copy of data. We can try use this feature instead of calling to_vec, to_bytes everywhere. For example, our decoder can accept std::io::Read instead of &[u8].

There are some places for opendal to improve like into_futures_async_read requires Range<u64>. We have fixed it and will be included in next release.

[Xuanwo]

For PrometheusLayer, I raised #4041

[tisonkun]

@Xuanwo seems we have two test cases failed:

• test_orc_opener - Footer length is empty
• test_object_store_cache_policy - file not found: ecfe0dce85de452eb0a325158e7bfb75.cache-bytes=7-4194310

The former seems related to ORC read content, the latter seems related to range encoding.

Would you help take a look?

[Xuanwo]

cache test should be fixed by tisonkun#6

Note, there is no 0.. read anymore.

[tisonkun]

@Xuanwo Thank you and integrated. Could you cross-link the OpenDAL PR that can fix the hack you mention in tisonkun#6?

[Xuanwo]

@Xuanwo Thank you and integrated. Could you cross-link the OpenDAL PR that can fix the hack you mention in tisonkun#6?

It happens in apache/opendal#4634

[codecov]

Codecov Report

Attention: Patch coverage is 83.68580% with 54 lines in your changes are missing coverage. Please review.

Project coverage is 85.11%. Comparing base (20ce7d4) to head (f9d5f78).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4037      +/-   ##
==========================================
- Coverage   85.43%   85.11%   -0.33%     
==========================================
  Files         985      985              
  Lines      170515   170571      +56     
==========================================
- Hits       145687   145182     -505     
- Misses      24828    25389     +561     

[killme2008]

It seems that there are a few tasks waiting for the opendal 0.4.7 release. I believe we should postpone this PR until then.

[tisonkun]

It seems that there are a few tasks waiting for the opendal 0.4.7 release. I believe we should postpone this PR until then.

@Xuanwo Is this regression from 0.45 to 0.46?

• build(deps): upgrade opendal to 0.46 #4037 (comment)

If not, I'd prefer we upgrade to 0.46, and then 0.47 as it's expected to release in the next few weeks:

• https://lists.apache.org/thread/s4w9okds2mknhjgkdcxyhy2nbyr0yd6d
• Tracking issues of OpenDAL 0.47.0 Release apache/opendal#4640

[Xuanwo]

Is this regression from 0.45 to 0.46?

No, I don't think it's a regression. The current behavior is expected. OpenDAL 0.47 simply introduces some additional improvements, for example, allow users calling into_futures_async_read with size.

[evenyag]

@Xuanwo Thanks for helping us to upgrade OpenDAL. I left some non-blocking comments to remind us after we merge this PR.

[tisonkun]

@killme2008 as this won't introduce explicit regression. I'd prefer we upgrade to 0.46, and then 0.47 as it's expected to release in the next few weeks.

See #4037 (comment).

[WenyXu]

By the way, I'm fixing the failed CI in #4049.🥲

[WenyXu]

LGTM