[
https://issues.apache.org/jira/browse/IMPALA-5973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16877392#comment-16877392
]
Jiawei Wang commented on IMPALA-5973:
-------------------------------------
Hi [~grahn],
I just noticed that there is a function in our code have done the job for us.
Which is the PlanToJson() function. This seems to be used for the query_plan
page. Do you have an idea if this is going to be useful or do we need to modify
it?
[https://github.com/apache/impala/blob/2164244a75189622085fe0319be4acd7185795f6/be/src/service/impala-http-handler.cc#L696|https://www.google.com/url?q=https://github.com/apache/impala/blob/2164244a75189622085fe0319be4acd7185795f6/be/src/service/impala-http-handler.cc%23L696&sa=D&ust=1562119418053000&usg=AFQjCNEf7JL9aLfreJpw1bCcfOfJpD9rvA]
> Provide query plan in JSON format
> ---------------------------------
>
> Key: IMPALA-5973
> URL: https://issues.apache.org/jira/browse/IMPALA-5973
> Project: IMPALA
> Issue Type: New Feature
> Components: Frontend
> Affects Versions: Impala 2.10.0
> Reporter: Alexander Behm
> Priority: Major
> Labels: planner
>
> Today there is only a text representation of the query plan, but it would be
> useful to have a JSON version for portability and machine consumption.
> To control whether EXPLAIN should produce a text or JSON output we could
> augment the EXPLAIN syntax or we could introduce a query option. It's worth
> discussing which one makes more sense.
> To avoid maintaining two code paths for explain (TEXT and JSON), I recommend
> that internally our code should always generate the JSON plan, and then have
> a function that can convert the JSON plan to the conventional textual
> representation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
