High Priority Dependency Updates Of Beam Python SDK:
Dependency Name
Current Version
Latest Version
Release Date Of the Current Used Version
Release Date Of The Latest Release
JIRA Issue
google-cloud-datastore
1.7.4
1.12.0
Absolutely Adham! I am doing very well.
I recommend starting with
https://issues.apache.org/jira/browse/BEAM-4152 (Session
Windowing), as understanding how that needs to be plumbed through would be
helpful in implementing https://issues.apache.org/jira/browse/BEAM-3304 as
well to a lesser extent.
Thanks a lot Robert! I really appreciate this awesome response
Regarding the Jira Account
My username is adhaamehab
I sent an email to get contributor permission and waiting for it any moment now.
I’ll assign the tasks for myself once I get that.
Kind Regards
Adham Ehab
> On Jul 6, 2020, at
I've added you as a contributor. Welcome!
-P.
On Mon, Jul 6, 2020 at 9:21 AM Adham Ehab wrote:
> Hi,
>
> Can someone add me as a contributor for beam’s Jira issue tracker?
> I would like to create/assign tickets for myself as I’m very interested
> in the *go-sdk.*
>
> my username is:
How did the experiment go? The load status graphs on the executors seem to
show no increase in queued jobs [1]. There is a periodic bump every 6h,
possibly due to cron firing off a bunch at the same time, that can also be
seen by changing the timepsan in [1]. The number of executors on 1/4 of the
Hi,
Can someone add me as a contributor for beam’s Jira issue tracker?
I would like to create/assign tickets for myself as I’m very interested in the
go-sdk.
my username is: adhaamehab
Thanks and Kind Regards,
Adham
Done.
On Wed, Jul 1, 2020 at 5:40 PM Valentyn Tymofieiev
wrote:
> Can somebody please add my pypi username (tvalentyn) to the list of
> apache-beam maintainers on PyPi: https://pypi.org/project/apache-beam/ ?
> Thank you!
>
> On Wed, Jul 1, 2020 at 4:51 PM Valentyn Tymofieiev
> wrote:
>
>>
+1 for removing Python 2.7 support sooner than later.
I recently added a small feature in Beam Python and I found that having to
write code that worked with Python2 was quite awkward and time consuming
(needing to make sure code works for both 2 and 3 and doubling the Jenkins
running time), and I
This sounds useful to me, and as it's purely informational would be a
low cost to try out. The one question is how it would impact build
runtimes--do you have an estimate for what the cost is here?
On Sun, Jul 5, 2020 at 1:14 PM Saavan Nanavati wrote:
>
> Hey everyone,
>
> Currently, during the
The idea was to add coverage to one of the already run precommit tox tasks.
This should keep the additional overhead to a minimum.
py37-cloud is the current candidate, since it contains the most
dependencies so fewer tests are skipped.
Saavan, do you have an estimate for the overhead?
Once
Note that just because Beam drops 2.x support in new releases doesn't
mean that the old releases won't continue to work. One can even use an
expansion service to run 2.x transforms (on an older version of Beam)
within a Python 3 pipeline running the newest version of Beam until
such a time that
I wouldn't consider build time as a blocker to add report. Even if build
time is rather slower, we can run coverage report periodically as a
separate job and still get use of it.
On Mon, Jul 6, 2020, 2:38 PM Robert Bradshaw wrote:
> This sounds useful to me, and as it's purely informational
12 matches
Mail list logo
