Nakadi SQL has a REST API where users can create and read SQL queries
The query is identified by the output event type name.
SQL query cannot be changed (for now).
SQL query has a state (active/inactive etc) that we can show.
We have parameterized monitoring ZMON dashboard per query.
Requirements
Create new SQL Query using the SQL editor, set name +required event type fields(name, audience, authorization ..etc)
The user should see the details of the query on the details page of the output event type.
Implementation
We will extend Nakadi UI to support new API(new config options/models/etc)
As Nakadi SQL is not open sources yet. New SQL related functionality should be hidden using feature flag in Nakadi UI config.
Add “SQL Query” to “Create” drop-down
Add new form for creating SQL query. The form contains Name input, SQL editor (preferably with the syntax highlight ), audience select, access control(READ/ADMIN only).
After the query is created, the user will be redirected to the output event type details page
Add a new tab to the Event Type details page “SQL”. it will be shown only if the current ET name exists in SQL API.
This tab will contain SQL view, status, and the link to the monitoring dashboard.
Questions
how to edit access control later?
Can we implement DRY RUN to validate SQL before sending it? (in the middle of sql edit process)
SergKam
commented
5 years ago
Nakadi SQL API (not opensources yet) https://github.bus.zalan.do/aruha/nakadi-sql-api/blob/master/docs/_data/nakadi-sql-api-definition.yaml
Introduction
Nakadi SQL has a REST API where users can create and read SQL queries The query is identified by the output event type name. SQL query cannot be changed (for now). SQL query has a state (active/inactive etc) that we can show. We have parameterized monitoring ZMON dashboard per query.
Requirements
Create new SQL Query using the SQL editor, set name +required event type fields(name, audience, authorization ..etc) The user should see the details of the query on the details page of the output event type.
Implementation
We will extend Nakadi UI to support new API(new config options/models/etc) As Nakadi SQL is not open sources yet. New SQL related functionality should be hidden using feature flag in Nakadi UI config. Add “SQL Query” to “Create” drop-down Add new form for creating SQL query. The form contains Name input, SQL editor (preferably with the syntax highlight ), audience select, access control(READ/ADMIN only). After the query is created, the user will be redirected to the output event type details page Add a new tab to the Event Type details page “SQL”. it will be shown only if the current ET name exists in SQL API. This tab will contain SQL view, status, and the link to the monitoring dashboard.
Questions
how to edit access control later? Can we implement DRY RUN to validate SQL before sending it? (in the middle of sql edit process)