ekuiper
ekuiper copied to clipboard
lf-edge
Will we support explain to show the query plan?
What would you like to be added/modified:
To support EXPLAIN in SQL.
Why is this needed: To show the query plan of SQL.
There is a REST API to show the query plan in runtime https://ekuiper.org/docs/en/latest/operation/restapi/rules.html#get-the-topology-structure-of-a-rule
As explain is supported in most DBMS, I think it worth to be supported in ekuiper too.
Maybe I can help.
As
explainis supported in most DBMS, I think it worth to be supported in ekuiper too. Maybe I can help.
A thousand welcomes
Starting investigate it. My first plan is to support some SQL to show the rule info as the REST API do. Does it help? My original idea is to support explain for SQL query. But it looks like more work need to be done. Since I'm not familliar with ekuiper, I guess I should start up with some easier cases.
However, my concern is that use SQL to show rules info is not in SQL standard. But I'm pretty sure it's a nice feature to support. If you agree, I will create a new issue to discuss the detail and update the progress. And let's keep this issue for future work about explain.
@ngjaying @superrxan
Sure. Currently, we add feature design doc at the LF Edge wiki https://wiki.lfedge.org/display/EKUIPER/Feature+Design+Proposals. You can also add your ideas there.
Sure. Currently, we add feature design doc at the LF Edge wiki https://wiki.lfedge.org/display/EKUIPER/Feature+Design+Proposals. You can also add your ideas there.
So if I understand it correctly, the SQL standard won't be an issue to be concerned?
My proposal will go something like allowing user to write SQL like describe rules where id = ${target_id} to get the rules topo. If it is reasonable I'll add it to the wiki as well as create a related issue.
@Yisaer Hi. Are you guys considering support explain grammar in ekuiper now?