This repository has been archived by the owner on Nov 18, 2024. It is now read-only.
Planned ideas for APIs #410
huachaohuang
started this conversation in
General
Replies: 1 comment 2 replies
-
I have two questions,
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Let me write down some planned ideas for APIs that are not going to deliver in 0.3 here.
Strongly-typed collections
The benefits of strongly-typed collections:
However, the currently supported collections are actually dynamically-typed despite the type notation in clients. This means that the server doesn't guarantee that all objects in the collection have the same type.
To support strongly-typed collections, we need to allow users to specify the type when they create collections.
Conditional transactions
The easiest to understand conditions are something like compare-and-swap (CAS). The Rust API maybe some like this:
Selection / Projection
The current APIs mostly focus on writes. We should support more advanced collection-level read operations. We can model the interface from Rust
Iterator
. For example, we may allow users to do this:Container member operations
We may allow users to do more operations on container members. For example, if we have a collection with the type
List<Int64>
, we can support something like:Support object options
For example, TTL
Beta Was this translation helpful? Give feedback.
All reactions