Read batch_max_operations from config instead

[Xuanwo]

As discussed in #2227, batch_max_operations could be different for diffent services, so we should allow users to configure it instead.

Actions

We should add new batch_max_operations config for service and use default value if not set.

Tasks

• fix(services/s3): Fix s3 batch max operations #2418
• fix(services/oss): Fix oss batch max operations #2414
• fix(services/azblob): Fix azblob batch max operations #2434

[manulpatel]

Hello @Xuanwo! I am new to OpenDAL community and would like to work on this issue.

[Xuanwo]

Great, we can start with add support for s3 first!

[manulpatel]

Hello @A-Stupid-Sun! You can continue to work on this issue and develop remaining 2 functionalities. Very Sorry @Xuanwo, I was occupied with other things, since last few days and not able to give time on this.

[A-Stupid-Sun]

Hello @A-Stupid-Sun! You can continue to work on this issue and develop remaining 2 functionalities. Very Sorry @Xuanwo, I was occupied with other things, since last few days and not able to give time on this.

no problem, I just start learning rust and your contribution give me much inspiration to fix it, thanks a lot！

[manulpatel]

Great! You can use my branch for s3 and close it soon.

[Xuanwo]

Very Sorry @Xuanwo, I was occupied with other things, since last few days and not able to give time on this.

That's ok, take your time and have fun! There is no sorry needed here.

[A-Stupid-Sun]

hi @Xuanwo, I wonder if it's necessary to add a new "batch_max_operations" config for the azbolb service ?
if it's necessary , I'm willing to fix it to close this issue.

[Xuanwo]

Thanks a lot! Let's do this.

[Xuanwo]

Thanks to @A-Stupid-Sun, all issues have been resolved. Closing now!