Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.1.0-rc0
Affects Version/s: None
Component/s: QueryTester
Labels:
None

Assigned Teams:

Query Optimization
Backwards Compatibility:
Fully Compatible
Sprint:
QO 2024-11-11, QO 2024-11-25, QO 2024-10-28
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

When a lot of tests fail in a QueryTester run, communicate (along with the list of failing queries) some metadata about query features to help users come to a solution more quickly. This could include info such as how many failing queries contained a sort, undergo a particular optimization, or contain a specific stage. Ideally, we should be able to use the feature-extractor, or a more lightweight query analyzer.

related to

SERVER-98325 Deduplicate failedQueryIds in QueryTester debugging output

Closed

SERVER-98360 Update --extractFeatures to use full failPath and refine feature summary to ignore "sort" and "limit"

Closed

SERVER-98361 Add option -v to QueryTester evergreen runs for verbose error output

Closed

SERVER-98364 Annotate individual queries with feature info in the case of failure

Closed

SERVER-97482 Add better error messages and exception handling to QueryTester feature extraction

Closed

SERVER-97484 Separate -v and --extract-from-features command line flags for QueryTester

Closed

(1 related to)

Assignee:: Lynne Wang
Reporter:: Lynne Wang
Participants:: Githook User, Lynne Wang
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Oct 25 2024 07:15:14 PM UTC
Updated:: Dec 11 2024 08:50:41 PM UTC
Resolved:: Nov 21 2024 05:21:13 PM UTC
Confidence Status Last Update:: 05/Nov/24 8:24 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates