You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Lukasz Cwik <lc...@google.com> on 2019/08/09 15:55:00 UTC
Re: Late data handling in Python SDK
+dev <de...@beam.apache.org>
Related JIRA's I found are BEAM-3759 and BEAM-7825. This has been a
priority thing as the community has been trying to get streaming Python
execution working on multiple Beam runners.
On Wed, Aug 7, 2019 at 2:31 AM Sam Stephens <sa...@gmail.com> wrote:
> Hi all,
>
> I’ve been reading into, and experimenting with, the Python SDK recently. I
> see that late data handling is not supported currently, but I can’t find
> where the progress of this feature is tracked: either in the portability
> support matrix or in Beam’s Jira. Can anyone help me there?
>
> If the answer is that there isn’t a single place to see this, my
> question is then: what is the current status of this? Is there some
> underlying difficult problem that has to be solved first or is it just a
> priority thing?
>
> Thanks
> Sam
>
Re: Late data handling in Python SDK
Posted by Tanay Tummalapalli <tt...@gmail.com>.
Hi Lukasz,
I'm currently working on BEAM-7742[1].
I'll work on BEAM-3759 afterwards.
Regards,
- Tanay
[1] https://issues.apache.org/jira/browse/BEAM-7742
On Fri, Aug 9, 2019 at 9:25 PM Lukasz Cwik <lc...@google.com> wrote:
> +dev <de...@beam.apache.org>
>
> Related JIRA's I found are BEAM-3759 and BEAM-7825. This has been a
> priority thing as the community has been trying to get streaming Python
> execution working on multiple Beam runners.
>
> On Wed, Aug 7, 2019 at 2:31 AM Sam Stephens <sa...@gmail.com>
> wrote:
>
>> Hi all,
>>
>> I’ve been reading into, and experimenting with, the Python SDK recently.
>> I see that late data handling is not supported currently, but I can’t find
>> where the progress of this feature is tracked: either in the portability
>> support matrix or in Beam’s Jira. Can anyone help me there?
>>
>> If the answer is that there isn’t a single place to see this, my
>> question is then: what is the current status of this? Is there some
>> underlying difficult problem that has to be solved first or is it just a
>> priority thing?
>>
>> Thanks
>> Sam
>>
>