[
https://issues.apache.org/jira/browse/DRILL-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Rogers updated DRILL-5232:
-------------------------------
Summary: Query profile should provide physical plan as JSON (was: In query
profile, provide physical plan as JSON)
> Query profile should provide physical plan as JSON
> --------------------------------------------------
>
> Key: DRILL-5232
> URL: https://issues.apache.org/jira/browse/DRILL-5232
> Project: Apache Drill
> Issue Type: Improvement
> Affects Versions: 1.9.0
> Reporter: Paul Rogers
> Priority: Minor
>
> The query profile contains two kinds of information:
> * The query plan, presented as text
> * The final status of each operator execution (AKA record batch) as JSON
> When working with the profile programmatically, it is quite easy to obtain
> information from the JSON-encoded operator profiles. But, the plan requires
> text parsing to turn the text plan into a series of fields.
> Since the plan starts as JSON, simply include that plan in the query profile
> to ease tool development.
> If needed for backward compatibility, the plan can continue to include the
> text version. Or, perhaps make the JSON version an option to be turned on
> when needed (though that causes problems when one wants to investigate an
> issue after the fact...)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
