drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Rogers (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DRILL-5233) Query profile should provide id to relate plan, profile elements
Date Sat, 28 Jan 2017 23:26:25 GMT
Paul Rogers created DRILL-5233:
----------------------------------

             Summary: Query profile should provide id to relate plan, profile elements
                 Key: DRILL-5233
                 URL: https://issues.apache.org/jira/browse/DRILL-5233
             Project: Apache Drill
          Issue Type: Improvement
    Affects Versions: 1.9.0
            Reporter: Paul Rogers
            Priority: Minor


The query profile contains two sections: a text representation of the physical plan, and a
series of JSON-serialized profiles for each minor operator (AKA record batch.)

It is difficult, however, to relate the two in code. The plan contains no numeric ID that
can be used to link the plan description of an operator with the profile element for that
operator. Instead, one must count the spaces used for indentation, do a bit of math, and use
that to infer an ID that maps to the "operatorId" in the JSON profile.

This requests asks to add the operatorID to the plan portion.

An ID exists, but it is something else entirely, a five-digit number that appears to not related
to anything else in the profile.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message