Azure / Azure/data-api-builder
Can't configure the partition key when defining the object model
Open
cosmos
engine
enhancement
graphql
- Dominant language
- C#
- Stars
- 1.5k
- Forks
- 370
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 9
Description
Cosmos backends require you to have a partition key of `id`, but there are many approaches to partitioning in Cosmos.
The developer should be able to define what it is when they are creating the GraphQL schema, maybe using a `@partitionKey` directive.
Contributor guide
Research direction
Start by reviewing how the GraphQL schema defines object models and how the Cosmos backend currently handles the required `id` partition key. The issue is complete when developers can specify a different partition key while creating the schema, potentially through a `@partitionKey` directive, and Cosmos requests use that definition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp, graphql
- Domain
- api, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100