Work for this feature has been started. Will update here when this feature becomes generally available.
Would like to double confirm, will the uniqueness scope to a partition, or among all partition?
Both Mongo API, SQL API allow user to set "unique keys" to ensure data integrity, it would be great if Gremlin API can also support this, otherwise it's hard to support concurrency.
This is now on our road map and is planned for our Fall development semester.
Thank you for your suggestion and votes.
Switch from Janus Graph to COSMOSDB relief me from maintaining a deployment, which is really great. However, Janus natively supports transaction and many existing business logic heavily relies on that: query to uncommitted vertex/edge, rollback entire transaction once any faulty state.
Also, if each query will go to COSMOSDB server, the latency from an entire business flow is really unacceptable. So I'm thinking if CosmosDB could provide a more sophistic client to handle transaction and cache?
(we're trying to achieve this by ourselves, but for complex query we found it really complicated. But I think CosmosDB already have much knowledge on graph compute, so it would be great this capability can be provided by CosmosDB team)
Reopening this user voice item as our support for Skip/Take (Offset/Limit) was only limited to single partition queries.
The newly released .NET SDK v3 now includes support for x-partition queries using Offset/Limit. You can learn more about v3 SDK and try it and provide feedback on our github repo here.
We will also be back-porting this functionality to our .NET v2 SDK. This work will begin shortly and we anticipate it to be released in September.
Once that is released we will mark this feature as complete.
Thank you for your patience and votes.
Hello, the item for this feature, will it also benefit Gremlin API once it's ready? Would really love this feature for gremlin API
Thank you for your feedback. We’re considering this for a future release of Azure Search.
Azure Search Product Team