[
https://issues.apache.org/jira/browse/IMPALA-5973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong reassigned IMPALA-5973:
-------------------------------------
Assignee: (was: Pranay Singh)
> 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: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
