[SERVER-75174] Serialize query shape for DocumentSourceSingleDocumentTransformation Created: 23/Mar/23 Updated: 29/Oct/23 Resolved: 11/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Davis Haupt (Inactive) | Assignee: | Maddie Zechar |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Query Optimization
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v6.3
|
||||||||||||
| Sprint: | QO 2023-04-17 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
This document source holds on to a TransformerInterface which knows how to serialize itself. The issue is that the implementations of TransformerInterface hold on to projection executors which represent the projection after optimization and lowering from the projection AST, which is later discarded. The query shape spec dictates that the query shape "should be calculated by serializing the first parsed query representation we have. For example, a MatchExpression, a projection_ast::Projection, or a Pipeline." Therefore, this ticket will need to modify the TransformerInterface to additionally hold on to a `projection_ast::Projection` so that it can serialize that structure instead in the case that the serialization options indicate that the query shape should be shapified/redacted. |
| Comments |
| Comment by Alexander Ignatyev [ 19/May/23 ] |
|
This change fix aggregation_optimization_fuzzer failings on v6.3 (BF-28652). |
| Comment by Githook User [ 10/Apr/23 ] |
|
Author: {'name': 'Maddie Zechar', 'email': 'mez2113@columbia.edu', 'username': ''}Message: |