beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Hyde (JIRA)" <>
Subject [jira] [Commented] (BEAM-301) Add a Beam SQL DSL
Date Thu, 06 Apr 2017 15:48:41 GMT


Julian Hyde commented on BEAM-301:

{{EMIT}} is just slide-ware at this point. I don't plan to start work on parsing/validating
it until we have nailed down the specification. Can someone from the Beam side check that
it captures the main triggering functionality?

I take your point about {{STREAM}}. Note that on the slide, {{EMIT WHEN COMPLETE}} is basically
the converse of {{STREAM}}. So, we might end up keeping {{STREAM}} as an alternative way of
specifying {{EMIT EARLY}} (or something).

Without the {{STREAM}} keyword to distinguish them, how would you phrase the queries {code}SELECT
STREAM * FROM Orders WHERE units > 100{code} (a streaming query, returning only orders
received from now on, and not terminating) and {code}SELECT COUNT(DISTINCT productId) FROM
Orders WHERE EXTRACT(YEAR FROM rowtime) = 2015{code} (a historical query, which emits one
row and terminates).

> Add a Beam SQL DSL
> ------------------
>                 Key: BEAM-301
>                 URL:
>             Project: Beam
>          Issue Type: New Feature
>          Components: sdk-ideas
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Xu Mingmin
> The SQL DSL helps developers to build a Beam pipeline from SQL statement in String directly.

> In Phase I, it starts to support INSERT/SELECT queries with FILTERs, one example SQL
as below:
> {code}
> {code}
> A design doc is available at

This message was sent by Atlassian JIRA

View raw message