[SERVER-42104] add flag to query result document indicating a COLSCAN was necessary Created: 03/Jul/19 Updated: 06/Dec/22 Resolved: 31/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Marco Ellwanger | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Query
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Currently the only way to detect COLSCANs is either to run an explain before or to parse the logs. The only way to disable COLSCANs is on the database level via a flag. If we had an indication on the query result that a COLSCAN occurred, then flexible handling on a case-by-case basis depending on other metrics would be much easier than having to sift through the logs on a regular basis after the fact. The driver should know that information for each query after execution anyways, why not expose it? Thanks |
| Comments |
| Comment by Craig Homa [ 31/Jul/19 ] |
|
Closing as this is confirmed to be a duplicate of SERVER-1812. |
| Comment by Danny Hatcher (Inactive) [ 08/Jul/19 ] |
|
Thanks for the feature request. I'll forward it on to our Query team to take a look. |