Hi,
I'm Sebastian, working for Trifacta. We use Beam for dataflow jobs in Cloud
Dataprep. Could someone add me as a contributor to jira? My jira id is sgrj.
Thanks,
Sebastian
Hi Sebastian,
Welcome! I've added you as a contributor in JIRA.
Cheers,
Max
On 14.08.19 11:54, Sebastian Jambor wrote:
> Hi,
>
> I'm Sebastian, working for Trifacta. We use Beam for dataflow jobs in
> Cloud Dataprep. Could someone add me as a contributor to jira? My jira
> id is sgrj.
>
> Than
Thanks Max!
On Wed, Aug 14, 2019 at 12:47 PM Maximilian Michels wrote:
> Hi Sebastian,
>
> Welcome! I've added you as a contributor in JIRA.
>
> Cheers,
> Max
>
> On 14.08.19 11:54, Sebastian Jambor wrote:
> > Hi,
> >
> > I'm Sebastian, working for Trifacta. We use Beam for dataflow jobs in
> >
Yes, that makes sense. What do you think about creating a document to
summarize the ideas presented here? Also, it would be good to capture
the status quo regarding caching in the Python SDK.
-Max
On 13.08.19 22:44, Thomas Weise wrote:
> The token would be needed in general to invalidate the cach
For the purpose of my own understanding of the matter, I've created a
document:
https://docs.google.com/document/d/1ltVqIW0XxUXI6grp17TgeyIybk3-nDF8a0-Nqw-s9mY/
It could make sense to clarify and specify things in there for now. I'm
more than willing to consolidate this document with the caching
Ahmet, thanks for forwarding!
> My main concern at this point is the introduction of new concepts, even
> though these are not changing other parts of the Beam SDKs. It would be
> good to see at least an alternative option covered in the design document.
> The reason is each additional concept ad
Q1:
The document is shared
(https://docs.google.com/document/d/1DYWrT6GL_qDCXhRMoxpjinlVAfHeVilK5Mtf8gO6zxQ/edit?usp=sharing).
If inside Google, short link (go/ibeam-external). I cannot share internal
documents, but you can reach out if you need internal engineering plan.
Q2:
Yes, watch() is op
Hi everyone,
Please review and vote on the release candidate #1 for the version 2.15.0,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
The complete staging area is available for your review, which includes:
* JIRA release notes [1].
*
Can we rebuild to include the fix for
https://issues.apache.org/jira/browse/BEAM-7866 which was merged yesterday
? (looks like fix version was changed to 2.16.0)
Thanks,
Cham
On Wed, Aug 14, 2019 at 1:42 PM Yifan Zou wrote:
> Hi everyone,
> Please review and vote on the release candidate #1 for
Sure. Would you please merge it to release-2.15.0, and I'll rebuild
artifacts and share the RC2?
On Wed, Aug 14, 2019 at 1:53 PM Chamikara Jayalath
wrote:
> Can we rebuild to include the fix for
> https://issues.apache.org/jira/browse/BEAM-7866 which was merged
> yesterday ? (looks like fix vers
Thanks Yifan.
FYI PR was merged: https://github.com/apache/beam/pull/9342
On Wed, Aug 14, 2019 at 2:32 PM Yifan Zou wrote:
> Sure. Would you please merge it to release-2.15.0, and I'll rebuild
> artifacts and share the RC2?
>
> On Wed, Aug 14, 2019 at 1:53 PM Chamikara Jayalath
> wrote:
>
>>
The release announcement blog should be part of the review as well.
On Wed, Aug 14, 2019 at 2:44 PM Chamikara Jayalath
wrote:
> Thanks Yifan.
>
> FYI PR was merged: https://github.com/apache/beam/pull/9342
>
>
>
> On Wed, Aug 14, 2019 at 2:32 PM Yifan Zou wrote:
>
>> Sure. Would you please mer
Hi Ning!
Thanks for the design doc and the explanations.
I think I can grasp some of the concepts, but it is not yet 100% clear to
me why it's necessary to define a new abstraction to have interactivity.
Could you elaborate? Perhaps as a section in the doc? : )
A lot of the motivation for this d
13 matches
Mail list logo
