[
https://issues.apache.org/jira/browse/ASTERIXDB-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17936150#comment-17936150
]
ASF subversion and git services commented on ASTERIXDB-3224:
------------------------------------------------------------
Commit 0e310856484a45a5a2d1d639eabccfde61873ed2 in asterixdb's branch
refs/heads/master from Suryaa
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=0e31085648 ]
[ASTERIXDB-3224] Added support for printing logical plan in DOT format
- Added support in UI and API(s)
Change-Id: Ia6e37080a581292744ddd9030b294936513c15ac
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/19390
Tested-by: Jenkins <[email protected]>
Integration-Tests: Jenkins <[email protected]>
Reviewed-by: Ian Maxon <[email protected]>
> Add DOT as plan format output option
> ------------------------------------
>
> Key: ASTERIXDB-3224
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3224
> Project: Apache AsterixDB
> Issue Type: Wish
> Components: API - HTTP API
> Reporter: Glenn Justo Galvizo
> Priority: Major
> Labels: triaged
>
> We currently export our plan (through our API) as JSON or as a string. Our
> 19006 UI (AFAIK) currently parses the JSON string and builds a graph from
> that JSON, but a more robust approach would be to generate a DOT format
> string and use this to help generate our graph instead. There's a lot of
> tools out there for visualizing DOT strings, meaning that other interfaces /
> applications could also visualize query plans if they need to.
>
> We have a DOT format printer in our codebase that is currently unused, so it
> wouldn't be too much work on the API side-- not too sure how much work this
> would be on the 19006 UI side though.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
