[SERVER-40120] $fts Basic Functionality Created: 14/Mar/19 Updated: 25/Mar/19 Resolved: 25/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Evan Nixon | Assignee: | Evan Nixon |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | FTS | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Sprint: | Query 2019-03-25, Query 2019-04-08 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Scoped to basic functionality of $_internalFTSIdLookup and $_internalFTSMongotRemote, specifically that unrelated to metadata, correct sorting in sharding, configuration, and testing. |
| Comments |
| Comment by Evan Nixon [ 25/Mar/19 ] |
|
Closing this and breaking work up into linked tickets |
| Comment by Evan Nixon [ 25/Mar/19 ] |
|
david.storch I meant to have this represent a base implementation I could CR more quickly and build functionality on top of - and have the tickets you mention be "parent tickets" for all work for those two stages. Those two tickets would have "depends on" relationships with all work for the two stages
This ticket would be a "first cut" and better allow me to make a CR for https://jira.mongodb.org/browse/SERVER-40015 (which seems difficult to split into a CR otherwise). |
| Comment by David Storch [ 22/Mar/19 ] |
|
evan.nixon, how does this differ from the work tracked by |