Skip to content

Updated information about partition key collisions #214

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

gauravsaini-ms
Copy link
Contributor

Updated documentation about partition key collisions. Including information about using large partition keys to avoid 403's because of collisions.

Copy link
Contributor

Microsoft authors of articles need to make updates through the private repository, so the updates can be staged and validated by current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.

It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:

 Public repo URL: http://github.com/MicrosoftDocs/{docs-repo}
 Private repo URL: http://github.com/MicrosoftDocs/{docs-repo-pr}

We have closed this pull request. Please resubmit the updates through the private repo. For more information, see the contributor guide.

Copy link
Contributor

Learn Build status updates of commit c5ebe55:

⚠️ Validation status: warnings

File Status Preview URL Details
articles/cosmos-db/nosql/troubleshooting-conflict.md ⚠️Warning Details
articles/cosmos-db/large-partition-keys.md ✅Succeeded

articles/cosmos-db/nosql/troubleshooting-conflict.md

  • Line 27, Column 222: [Warning: file-not-found - See documentation] Invalid file link: '../../container-copy.md'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant