core: Add start-after for OpList and add into capability

[Xuanwo]

No description provided.

[Xuanwo]

cc @lexcao

[Xuanwo]

We can discuss the detials in this issue

[lexcao]

Hi @Xuanwo , this is my first time contributing to OpenDAL, I would like to discuss the details before coding, please feel free to correct me.

To support start-after param for List operation, we could make these changes:

1. Add start_after arg (with getter and setter) for OpList
2. Add list_with method with param OpList for Operator

I need help on how to

add into capability

What does that mean?

I just found the Capability is used on operations rather than a single argument.

[Xuanwo]

add into capability

We need to add a new field called list_with_start_after: bool to indicate that service support this arg.

[lexcao]

Thanks.
I find there is a option for batch parameter max_batch_operations in AccessorInfo

So the list_with_start_after is added to the AccessorInfo?
Then to add a warning log when the accessor does not support the arg but is presented in the OpList when calling list_with method.

---

I just found there is a way to support custom args by leveraging AccessorCapability

enum AccessorCapability {
    List { start_after: bool }
    ...
}

This needs to extend AccessorCapability to support this since currently it is just u32 enum.

With that, the max_batch_operations could be replaced by

Batch { max_operations: uszie }

But this is another topic, I don't know if this is a good practice or not.

[Xuanwo]

I'm guessing you need to update the main branch. We have a new Capacity design now.

[lexcao]

Great, thank you! My bad.
I am ready to code. 💪