#29 Nakadi SQL Query tab and server support added #30
Conversation
|
It will not be allowed to have 'any valid token' in admin section, maybe this can be a flag in the configuration? |
| OnInput | ||
| "Output Event Type Name" | ||
| "Example: bazar.price-updater.price_changed" | ||
| "Should be several words (with '_', '-') separated by dot." |
There was a problem hiding this comment.
no. I mean yes, but it is bad practice https://opensource.zalando.com/restful-api-guidelines/#223
| OnInput | ||
| "Owning Application" | ||
| "Example: stups_price-updater" | ||
| "App name registered in YourTurn with 'stups_' prefix" |
There was a problem hiding this comment.
the open source nakadi UI doesn't know what yourturn is :)
There was a problem hiding this comment.
but we don't have anything better for now.
cleanup from stups requires the additional ticket in the future. But I would keep it now for consistency reasons.
| , newline | ||
| , text "The SQL statements supported are a subset of ANSI SQL." | ||
| , newline | ||
| , text "The operations supported are joining two or more EventTypes and filtering" |
There was a problem hiding this comment.
I'm just a copycat :) https://github.bus.zalan.do/aruha/nakadi-sql-api/blob/master/docs/_data/nakadi-sql-api-definition.yaml#L186
fix the source.
| , text "The SQL statements supported are a subset of ANSI SQL." | ||
| , newline | ||
| , text "The operations supported are joining two or more EventTypes and filtering" | ||
| , text " EventTypes to an output EventType. The EventTypes on which these queries are run MUST" |
There was a problem hiding this comment.
Actually we are going to support filter and projection on all event types before going GA then open source. Joins are log-compacted only for now
There was a problem hiding this comment.
Then we will change it accordingly (maybe change will be bigger).
| span | ||
| [ onClick OpenDeleteQueryPopup | ||
| , class "icon-link dc-icon--trash dc-btn--destroy dc-icon dc-icon--interactive" | ||
| , title "Terminate Query" |
There was a problem hiding this comment.
I prefer "Deactivate Query"
There was a problem hiding this comment.
I choose this word because there is no opposite word like "unterminate" in opposite to "Activate/Reactivate" and "Stop". To suggest people that they cannot restart it later.
| [ text "Nakadi SQL API provides a self-serviceable SQL interface for stream processing Nakadi event" | ||
| , text " types. By expressing transformations as SQL, this service enables a broader audience to analyse" | ||
| , text " and process streaming data in real-time. Nakadi SQL is scalable, elastic and fault-tolerant." | ||
| , text " It's planned to support a wide range of streaming operations, including data filtering," |
There was a problem hiding this comment.
ok, but fix it in api.yaml
| , text " types. By expressing transformations as SQL, this service enables a broader audience to analyse" | ||
| , text " and process streaming data in real-time. Nakadi SQL is scalable, elastic and fault-tolerant." | ||
| , text " It's planned to support a wide range of streaming operations, including data filtering," | ||
| , text " transformations, aggregations, joins, windowing, and sessionization." |
There was a problem hiding this comment.
There was a problem hiding this comment.
it is a thing apparently https://www.dataiku.com/learn/guide/code/reshaping_data/sessionization.html
| , newline | ||
| , text "The output events are written to an output EventType, which can be accessed via Nakadi." | ||
| , newline | ||
| , link "More in the API Manual" "https://apis.zalando.net/apis/3d932e38-b9db-42cf-84bb-0898a72895fb/ui" |
There was a problem hiding this comment.
This isn't accessible for non-Zalandos
#29 Nakadi SQL Query tab and server support added