[SERVER-85089] User Summary for SERVER-45363 Created: 21/Jan/20 Updated: 12/Jan/24 Resolved: 28/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ted Tuckman | Assignee: | Ted Tuckman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Query 2020-01-27, Query 2020-02-10 | ||||||||
| Participants: | |||||||||
| Description |
|
Issue Status as of Jan 21, 2020 ISSUE SUMMARY USER IMPACT RECOVERY STEPS AFFECTED VERSIONS FIX VERSION |
| Comments |
| Comment by Ted Tuckman [ 27/Jan/20 ] |
|
I've copied the current version over to the server ticket, I'll duplicate any changes that are made from this point forward. |
| Comment by David Storch [ 23/Jan/20 ] |
|
This LGTM (after I made a few minor edits), with one more piece of feedback:
I'm not entirely sure what "next specified field in the index" means. It means the "next field for which a weight is specified in the index definition", right? |
| Comment by Charlie Swanson [ 23/Jan/20 ] |
|
ted.tuckman LGTM other than the following. I would add a link to the docs for "wildcard text index" and "weighted fields". I imagine some people would be unfamiliar with those terms and wondering if this impacted them. |
| Comment by Ted Tuckman [ 23/Jan/20 ] |
|
david.storch Good notes. I've made those changes, though if you're alright with it I'd probably remove the example and just leave is as "lexicographically smaller (alphabetically earlier) than ..." |
| Comment by David Storch [ 22/Jan/20 ] |
|
CC kelsey.schubert, since this is an issue you may want to be aware of. |
| Comment by David Storch [ 22/Jan/20 ] |
|
Thanks ted.tuckman! Two minor points of feedback:
|