[DRIVERS-1518] Investigate changes in PM-2135: Maintain sample or schema summary Created: 19/Jan/21 Updated: 22/Sep/21 Resolved: 20/Jan/21 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Epic | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Driver Changes: | Not Needed | ||||
| Description |
|
Downstream Change Summary This will have impact on ET teams, particularly BIC and Charts. Description of Linked TicketEpic Summary SummarySeveral tools including compass, schema advisor, and the Business Intelligence Connector all rely on using $sample to summarize the contents of a collection. $sample can be tricky to use in a performant way. We know of several workarounds implemented by these tools. Instead of repeatedly scanning the collection on-demand, we could maintain a certain sized sample or perhaps a summary schema as the contents of the collection change. MotivationHaving an accurate view of a MongoDB collection's schema is critical to the correct operation of the BI Connector (and now the $sql stage in Atlas Data Lake as well). Cast of Characters
DocumentationScope Document |