...
Jira |
---|
server | ASF JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
---|
key | STORM-1443 |
---|
|
Jira |
---|
server | ASF JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
---|
key | STORM-1446 |
---|
|
Jira |
---|
server | ASF JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
---|
key | STORM-2073 |
---|
|
Others (non-epic)
Jira |
---|
server | ASF JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
---|
key | STORM-2125 |
---|
|
Jira |
---|
server | ASF JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
---|
key | STORM-2099 |
---|
|
How this milestone will help users to play with Storm SQL?
- Users will be able to run Storm SQL Runner without copying dependencies to extlib.
- This is resolved from
Jira |
---|
server | ASF JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
---|
key | STORM-2016 |
---|
|
but this issue was originally came from Jira |
---|
server | ASF JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
---|
key | STORM-1435 |
---|
|
- Users will be able to use GROUP BY and JOIN statement in DML statement
- Note that these feature follows the Trident semantic of aggregation and join
- Aggregation is done within batch
- SQE does stateful aggregation, so Storm SQL might follow later
- Join is done with each of batches
- But respecting Streaming SQL semantic seems correct, which means that we could get rid of these features again and wait for Streaming SQL
- This is what Flink is doing, but Flink have Table API so Flink can support window aggregation and join without Calcite support
- Users will be able to use user defined aggregate function in Trident mode
- User defined function is already supported
- Users will be able to run 'explain' to see query plan for DML statement before submitting Trident topology
- Users will be able to specify parallelism of input data source which will be used unless repartitioning is made
- Users will be able to store rows to Redis
How this milestone will improve Storm SQL internally?
Jira |
---|
server | ASF JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
---|
key | STORM-2073 |
---|
|
will reduce redundant multiple Trident steps into one. Jira |
---|
server | ASF JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
---|
key | STORM-1446 |
---|
|
will do some query optimizations, and open the way to address next works, like automatic parallelism, pushdown, and so on Jira |
---|
server | ASF JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
---|
key | STORM-2125 |
---|
|
will enable most of functionalities what Calcite supports.- Except aggregate functions, but we may find the way to get them
Next works
Below works can be done without waiting some other works. We might want to pick several works from each category and create next milestone.
...