Re: [VOTE] Beam's Mascot will be the Firefly (Lampyridae)

+1 On Fri, Dec 13, 2019 at 5:58 AM Kenneth Knowles wrote: > Please vote on the proposal for Beam's mascot to be the Firefly. This > encompasses the Lampyridae family of insects, without specifying a genus or > species. > > [ ] +1, Approve Firefly being the mascot > [ ] -1, Disapprove Firefly

Re: Committed without review. Sorry.

Thanks for alerting dev@. IMO this was handled perfectly by all parties. Kenn On Thu, Dec 12, 2019 at 4:09 PM Valentyn Tymofieiev wrote: > The change LGTM, so you can consider it reviewed. In general it would be > nice to set up alerts to catch these situations, to make sure they don't go >

Re: [VOTE] Beam's Mascot will be the Firefly (Lampyridae)

+1 (non binding) On Thu, Dec 12, 2019 at 9:14 PM Robert Burke wrote: > +1 (non binding) > > On Thu, Dec 12, 2019, 8:58 PM Kenneth Knowles wrote: > >> Please vote on the proposal for Beam's mascot to be the Firefly. This >> encompasses the Lampyridae family of insects, without specifying a

Re: [VOTE] Beam's Mascot will be the Firefly (Lampyridae)

+1 (non binding) On Thu, Dec 12, 2019, 8:58 PM Kenneth Knowles wrote: > Please vote on the proposal for Beam's mascot to be the Firefly. This > encompasses the Lampyridae family of insects, without specifying a genus or > species. > > [ ] +1, Approve Firefly being the mascot > [ ] -1,

[VOTE] Beam's Mascot will be the Firefly (Lampyridae)

Please vote on the proposal for Beam's mascot to be the Firefly. This encompasses the Lampyridae family of insects, without specifying a genus or species. [ ] +1, Approve Firefly being the mascot [ ] -1, Disapprove Firefly being the mascot The vote will be open for at least 72 hours excluding

Re: [VOTE] Beam Mascot animal choice: vote for as many as you want

Ah! I forgot to send the official ratification vote. I will do that now. On Thu, Dec 12, 2019 at 3:51 PM Aizhamal Nurmamat kyzy wrote: > Thank you, Kenn for running the vote. I reached out to a couple community > members to see if they would like to develop the design and contribute it > to

Re: Cassandra IO issues and contributing

On Thu, Dec 12, 2019 at 3:30 PM Vincent Marquez wrote: > Hello, as I've mentioned in previous emails, I've found the CassandraIO > connector lacking some essential features for efficient batch processing in > real world scenarios. We've developed a more fully featured connector and > had good

Re: Unifying Build/contributing instructions

Thanks for taking this on! My preference would be to have CONTRIBUTING.md link to https://beam.apache.org/contribute/contribution-guide/ and focus work on the latter. Kenn On Thu, Dec 12, 2019 at 12:38 PM Elliotte Rusty Harold wrote: > I've started work on updating and combine the four (or

Re: [RELEASE] Tracking 2.18

Also marked 3 Jiras from these cherrypicks as blockers . Current open blocker count: 7 . On Thu, Dec 12, 2019 at 5:21 PM Udi Meiri wrote: > Just merged 6 PRs. :) > > On Thu, Dec 12, 2019 at 4:52 PM Udi Meiri wrote: > >> Update:

Re: [RELEASE] Tracking 2.18

Just merged 6 PRs. :) On Thu, Dec 12, 2019 at 4:52 PM Udi Meiri wrote: > Update: I'm accepting cherrypicks with failing tests if the corresponding > PR have passed them on master. > > I recall (without proof) that in the past, even with released worker > containers for the in-process release,

Re: Artifact staging in cross-language pipelines

I'm brushing up memory by revisiting the doc[1] and it seems like we've already reached the consensus on the bigger picture. I would start drafting the implementation plan. [1]: https://docs.google.com/document/d/1XaiNekAY2sptuQRIXpjGAyaYdSc-wlJ-VKjl04c8N48/edit?usp=sharing On Tue, Nov 26, 2019

Re: [RELEASE] Tracking 2.18

Update: I'm accepting cherrypicks with failing tests if the corresponding PR have passed them on master. I recall (without proof) that in the past, even with released worker containers for the in-process release, that ITs against the release branch still fail. On Tue, Dec 10, 2019 at 10:58 AM

Root logger configuration

Hello all, It has been pointed out to me by Chad, and also by others, that my logging changes have caused logs to start getting lost. It seems that by never logging on the root logger, initialization for a root handler is skipped; and that's what causes the failures. I will work on a fix for

Re: Committed without review. Sorry.

The change LGTM, so you can consider it reviewed. In general it would be nice to set up alerts to catch these situations, to make sure they don't go unnoticed. Also as a reminder - please don't commit or merge PRs into release branches without a review from a release manager. On Thu, Dec 12,

Re: [VOTE] Beam Mascot animal choice: vote for as many as you want

Thank you, Kenn for running the vote. I reached out to a couple community members to see if they would like to develop the design and contribute it to Beam. I will keep you all posted. Thanks :) On Mon, Dec 2, 2019 at 8:20 PM Kenneth Knowles wrote: > Hi all, > > I have tweaked Robert's python*

Re: Committed without review. Sorry.

Seed job runs okay: https://builds.apache.org/job/beam_SeedJob_Standalone/3865/console On Thu, Dec 12, 2019 at 3:28 PM Pablo Estrada wrote: > I accidentally committed a small change to master: > https://github.com/apache/beam/commit/6018326ffe74aac7d8c44ded296b92f8b5c0b556 > > I am verifying

Re: Beam's job crashes on cluster

Can you share the pipeline options you are using? Particularly environment_type and environment_config. On Thu, Dec 12, 2019 at 2:58 PM Matthew K. wrote: > Running Beam on Spark cluster, it crashhes and I get the following error > (workers are on separate nodes, it works fine when workers are

Cassandra IO issues and contributing

Hello, as I've mentioned in previous emails, I've found the CassandraIO connector lacking some essential features for efficient batch processing in real world scenarios. We've developed a more fully featured connector and had good results with it. Could I perhaps write up a JIRA proposal for

Committed without review. Sorry.

I accidentally committed a small change to master: https://github.com/apache/beam/commit/6018326ffe74aac7d8c44ded296b92f8b5c0b556 I am verifying that this works as intended for now. What should we do about this? Revert? Leave as is if it works fine? Best -P

Beam's job crashes on cluster

Running Beam on Spark cluster, it crashhes and I get the following error (workers are on separate nodes, it works fine when workers are on the same node as runner):   > Task :runners:spark:job-server:runShadow FAILED Exception in thread wait_until_finish_read: Traceback (most recent call last):

Unifying Build/contributing instructions

I've started work on updating and combine the four (or omre?) different pages where build instructions are found. The initial PR is here: https://github.com/apache/beam/pull/10366 To put a stake in the ground, this PR chooses CONTRIBUTING.md as the ultimate source of truth. A possible

Re: RFC: python static typing PR

Thanks for the kind words, everyone. Note that the PR that was merged was the first half, so the mypy-lint job is not yet setup to trigger failures. Part 2 is up now: https://github.com/apache/beam/pull/10367 My goal is to bundle up changes into smaller PRs from here on out. It might take

Re: Executing the runner validation tests for the Twister2 runner

Hi Kenn We are still working on aspects like automated job monitoring so currently do not have those capabilities built-in. I discussed with the Twister2 team on a way we can forward failure information from the workers to the Jobmaster which would be a solution to this problem. It might take a

Re: December board report

Kenn, I’d suggest to mention also a discussion about re-imagination of “@Experimental” annotation and stabilisation API in this sense. > On 12 Dec 2019, at 06:07, Kenneth Knowles wrote: > > Hi all, > > Late notice on this, but the December Board report is due "now". > > I've started a