For clarification, is it just streaming side inputs that present an issue for
SparkRunner or are there other areas that need work? We've started work on a
Beam-based project that includes both streaming and batch oriented work and a
Spark cluster was our choice due to the perception that it
Support for watermark holds is missing for both Spark streaming
implementations (DStream and structured streaming) so watermark based
triggers don't produce the correct output.
Excluding the direct runner, Flink is the OSS runner with the most people
working on it adding features and fixing bugs
Hi Artur,
Done. Welcome to Beam community!
Alexey
> On 2 Oct 2020, at 18:31, Artur Khanin wrote:
>
> Hi,
>
> This is Artur from Akvelon. Right now I am working on Dataflow templates in
> Apache Beam. Can someone add me as a contributor for Beam's Jira issue
> tracker? I would like to
Hi,
This is Artur from Akvelon. Right now I am working on Dataflow templates in
Apache Beam. Can someone add me as a contributor for Beam's Jira issue tracker?
I would like to create/assign tickets for my work.
My Jira ID: Artur.Khanin
Thanks,
Artur Khanin