[DOCS-14361] Compound Sparse Unique indexes behaviour is not properly specified Created: 14/Apr/21 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | 3.6.17 |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | moroine bentefrit | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-11701 |
| Description |
DescriptionThe documentation is not complete for compound sparse unique index. Documentation mention if the key is omitted, then it won't trigger an error. But that's not true for compound indexes where one key (but not all) is omitted: ```javascript = require('mongodb'); async function run() { , try { await db.dropCollection('scores').catch(() => { /* no-op */ });await db.dropCollection('scores-other').catch(() => { /* no-op */ } ); await db.collection('scores').createIndex( , , // Works ); ); try { ); ); try { ); ); } catch (err) { console.error(err); }finally { client.close(); }} run(); I am not sure if this requires a documentation update or a bug fix. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |