Azure / Azure/cosmos-explorer

Unique Keys can't be viewed once set

Open
#1,723 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
TypeScript
Stars
131
Forks
67
Avg merge
3d 13h
Merged PRs (30d)
10

Description

Hi there! This is definitely a case of hoping I'm wrong, but I can't seem to be able to see what Unique Keys have been defined for a container after the container's been created.

Example:
- Create a database called "myDatabse"
- Create a container called "myContainer" with a unique key of "/myUniqueKey"
- Once "myContainer" is created, I can't seem to view whether "myContainer" has any unique key policies, including that of "/myUniqueKey"

Through the Cosmos DB SDK I can query the container's UniqueKeyPolicy, but that doesn't appear to be possible through the Explorer.

Cheers!

Contributor guide

Open the contributing guide

Research direction

Start in the Azure Cosmos DB Explorer container-details UI and trace how the created container's metadata is displayed. Compare the available Explorer information with the SDK's UniqueKeyPolicy behavior described in the issue. Done means a created container clearly shows whether unique key policies exist and includes the configured /myUniqueKey example.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
databases, frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.