[DOCS-14472] Document that update operators that act on multiple paths act in lexographic order for versions <= 4.4 Created: 19/May/21 Updated: 13/Nov/23 Due: 17/Sep/21 Resolved: 14/Sep/21 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Sam Mercier | Assignee: | Joseph Dougherty |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Days since reply: | 2 years, 19 weeks ago | ||||||||||||||||
| Epic Link: | DOCSP-11702 | ||||||||||||||||
| Story Points: | 3 | ||||||||||||||||
| Description |
DescriptionIf the documentation team doesn't think that this will clutter the documentation, it would be nice if we could document for versions of the databases <= 4.4 operators which act on multiple paths will act on them in lexographic order (so "a.10" before "a.2"). In the future ,these updates will happen in numeric order if a path component is entirely composed of numbers (so "a.2" before "a.10"). Scope of changesI think we'll want to update:
Maybe also consider a note/include to be added to the Behavior section of affected update operators:
Impact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 29/Sep/21 ] |
|
Author: {'name': 'jmd-mongo', 'email': '73852296+jmd-mongo@users.noreply.github.com', 'username': 'jmd-mongo'}Message: Docs 14795 update order numeric when possible (#5898)
|
| Comment by Githook User [ 20/Sep/21 ] |
|
Author: {'name': 'jeff-allen-mongo', 'email': 'jeffrey.allen@10gen.com', 'username': 'jeff-allen-mongo'}Message: Revert " This reverts commit 9200afee266c9d79d0dc01747c10aa0ee1eb3702. |
| Comment by Githook User [ 20/Sep/21 ] |
|
Author: {'name': 'jeff-allen-mongo', 'email': 'jeffrey.allen@10gen.com', 'username': 'jeff-allen-mongo'}Message: Revert " This reverts commit 9200afee266c9d79d0dc01747c10aa0ee1eb3702. |
| Comment by Githook User [ 20/Sep/21 ] |
|
Author: {'name': 'Joseph Dougherty', 'email': 'joseph.dougherty@mongodb.com', 'username': 'jmd-mongo'}Message: |
| Comment by Githook User [ 14/Sep/21 ] |
|
Author: {'name': 'Joseph Dougherty', 'email': 'joseph.dougherty@mongodb.com', 'username': 'jmd-mongo'}Message: |
| Comment by Ted Tuckman [ 26/Aug/21 ] |
|
Yes, all operators should implement this change. |
| Comment by Sam Mercier [ 23/Aug/21 ] |
|
joseph.dougherty i'm going to loop ted.tuckman in to confirm, but i believe so after reviewing this section of his changes. |
| Comment by Joseph Dougherty [ 23/Aug/21 ] |
|
Hello samuel.mercier, Are all the update operators affected here? If so, I can create an include/notice to let users know about the lexicographic processing order on the landing page as well as the individual command pages. Could you confirm all of the update operators are affected? Thanks for your help! |