[
https://issues.apache.org/jira/browse/BEAM-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132276#comment-17132276
]
Beam JIRA Bot commented on BEAM-3783:
-------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Streaming Beam SQL benchmarks on all of our runners
> ---------------------------------------------------
>
> Key: BEAM-3783
> URL: https://issues.apache.org/jira/browse/BEAM-3783
> Project: Beam
> Issue Type: New Feature
> Components: testing-nexmark
> Reporter: Kenneth Knowles
> Assignee: Kai Jiang
> Priority: P2
> Labels: SQL, bigdata, cloud, gsoc2018, java, stale-assigned
>
> Beam has a number of classic streaming SQL benchmarks known as "Nexmark"
> coded up in both raw Java and also Beam SQL.
> So far, expanding functionality has been the focus of Beam SQL so there is
> little known about performance - we know only that it is a pretty
> straightforward mapping from SQL to Beam that should work OK a lot of the
> time. It would be interesting to see where the bottlenecks are when these SQL
> benchmarks are translated via Beam SQL into a Beam pipeline and then again
> translated to the native capabilities of e.g. Spark and Flink.
> This project will require the ability to read, write, and run Java and SQL.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
