[SERVER-30030] Create a $_internalSchemaCond MatchExpression Created: 06/Jul/17 Updated: 30/Oct/23 Resolved: 21/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.11 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kyle Suarez | Assignee: | Kyle Suarez |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Query 2017-07-31 |
| Participants: |
| Description |
| Comments |
| Comment by Githook User [ 21/Jul/17 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: |
| Comment by Githook User [ 21/Jul/17 ] |
|
Author: {u'username': u'ksuarz', u'name': u'Kyle Suarez', u'email': u'kyle.suarez@mongodb.com'}Message: |
| Comment by Kyle Suarez [ 06/Jul/17 ] |
|
david.storch, let's go with your proposal of condition, thenBranch and elseBranch. I've updated the description accordingly. I agree that the naming isn't important, but would prefer to have names over a three-element array. In the event that someone has to debug this somewhere down the line, I would want the serialized versions of these MatchExpressions to be self-documenting and obvious. |
| Comment by David Storch [ 06/Jul/17 ] |
|
kyle.suarez, or condition, thenBranch, elseBranch, though I think the naming is not essential here. We could also require a three-element array. I'd be happy with any of these options. |
| Comment by Kyle Suarez [ 06/Jul/17 ] |
|
My only qualm is that if, then and else will be highlighted in a non-context-aware syntax highlighter... then again, aggregation $cond uses the same words. If we really care, we could call them condition, trueBranch, and falseBranch, or something to that effect. |