Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
1.12.0
-
None
-
None
Description
The minor fragments in the attached profile ( 258f4b68-62ec-78b8-5bac-9331cccfa5fa[1].json ) does not correctly mark the operator Id as 1 . It is defaulting to 0 (which, I suspect, means that the value was never set and is the default primitive value), making the WebUI count it as part of the Screen operator.
Also, the operatorType is incorrectly set as 10 ( PROJECT ) instead of 31 ( COMPLEX_TO_JSON )
*Original: *
{ "inputProfile": [ { "records": 1703936, "batches": 52, "schemas": 1 } ], "operatorId": 0, "operatorType": 10, "setupNanos": 2026811, "processNanos": 32199443, "peakLocalMemoryAllocated": 21639235, "waitNanos": 0 }
Correct:
{ "inputProfile": [ { "records": 1703936, "batches": 52, "schemas": 1 } ], "operatorId": 1, "operatorType": 31, "setupNanos": 2026811, "processNanos": 32199443, "peakLocalMemoryAllocated": 21639235, "waitNanos": 0 }
Attachments
Attachments
Issue Links
- Is contained by
-
DRILL-6185 Error is displaying while accessing query profiles via the Web-UI
- Closed