How does this mechanism differ from beam SQL which already offers windowing
via SQL over PCollections?

https://beam.apache.org/documentation/dsls/sql/extensions/windowing-and-triggering/

-Daniel

On Mon, Jun 12, 2023 at 3:11 PM Ryan Michael <keri...@gmail.com> wrote:

> Hello, Beam (also)!
>
> Just introducing myself - I'm Ryan and I've been working with Ben on the
> Kaskada project for the past few years. As Ben mentioned, I think there's a
> great opportunity to bring together some of the work we've done to make
> time-based computation easier to reason about with the Beam community's
> work on scalable streaming computation.
>
> I'll be at the Beam Summit in NYC starting Wednesday and presenting a
> short overview of how we see Kaskada fitting into the Generative AI world
> at the "Generative AI Meetup" Wednesday afternoon - if the doc Ben linked
> to (or GenAI) is interesting to you and you'll be at the conference I'd
> love to touch base in person!
>
> -Ryan
>
> On Mon, Jun 12, 2023 at 2:51 PM Ben Chambers <bchamb...@apache.org> wrote:
>
>> Hello Beam!
>>
>> Kaskada has created a query language for expressing temporal queries,
>> making it easy to work with multiple streams and perform temporally
>> correct joins. We’re looking at taking our native, columnar execution
>> engine and making it available as a PTransform and FnHarness for use
>> with Apache Beam.
>>
>> We’ve drafted a [short document][proposal] outlining our planned
>> approach and the potential benefits to Kaskada and Beam users. It
>> would be super helpful to get some feedback on this approach and any
>> ways that it could be improved / better integrated with Beam to
>> provide more value!
>>
>> Could you see yourself using (or contributing) to this work? Let us know!
>>
>> Thanks!
>>
>> Ben
>>
>> [proposal]:
>> https://docs.google.com/document/d/1w6DYpYCi1c521AOh83JN3CB3C9pZwBPruUbawqH-NsA/edit
>>
>
>
> --
> *Ryan Michael *
> keri...@gmail.com | 512.466.3662 <(512)%20466-3662> | github
> <https://github.com/kerinin> | linkedin
> <http://www.linkedin.com/pub/ryan-michael/21/41/a29>
>

Reply via email to