Re: Java Tests are failing on Github checks

Thank you all for fixing this! > On 8 Mar 2021, at 21:06, Ankur Goenka wrote: > > The fix PR https://github.com/apache/beam/pull/14148 > which upgrades the error prone > version to 2.3.4 with failing checks disabled seems to be working fine and is >

Re: [VOTE] Release vendor-calcite-1_26_0 version 0.1, release candidate #1

Thanks Brian I see that there are a lot of reasons to do the upgrade, maybe in the future it would be a good idea to explain the main motivations of the upgrade for vendored dependencies and refer relevant JIRAs On Tue, Mar 9, 2021 at 6:23 PM Brian Hulette wrote: > > There are several jiras block

[Question] Python SDK harness configuration

Hello! I'm having some problems configuring the python SDK harness when leaving from the "LOOPBACK" configuration with the Spark Runner. When using environment type = "EXTERNAL" I'm getting no configuration to the endpoints: ` Starting worker with command ['/opt/apache/beam/boot', '--id=1-1', '-

[Question]: How to write data to ScyllaDB

Hi, I have a use case to read data from Google BigQuery and write it to a table in Scylla DB. I checked that there is no IO available for Scylla DB in beam for now. Please guide me on how can this use case be build. Regards, Shivam -- Disclaimer: The information contained in this communication

[Question]: Using Asyncio with Python SDK

Hello, We are planning to use Beam Python SDK (with Dataflow) to export entities in the datastore to bigquery. We are using an in -house ORM library for datastore and it is async. I did a bit search to see whether it is possible to use async with Beam Python SDK but did not find it anywhere (neit

Re: [Question]: How to write data to ScyllaDB

Personally, I didn’t try to work with ScyllaDB from Beam, but looking at its wiki page: "Scylla is an open-source distributed NoSQL data store. It was designed to be compatible with Apache Cassandra while achieving significantly higher throughputs and lower latencies. It supports the same proto

User-related questions in dev@ list

Hello all, A quick question about our mailing lists policy. Quite often I see that people tend to send the user-related questions to dev@. For example: [1], [2] and many similar ones. I believe it’s a bad practice since it's mixing up with other dev-related threads and makes it difficult to s

Re: User-related questions in dev@ list

On Wed, Mar 10, 2021 at 10:36 AM Alexey Romanenko wrote: > Hello all, > > A quick question about our mailing lists policy. > > Quite often I see that people tend to send the user-related questions to > dev@. For example: [1], [2] and many similar ones. > > I believe it’s a bad practice since it's

Re: User-related questions in dev@ list

> What do you think should be the right behaviour for managing such emails? > Forward this email to user@ (and remove dev@ address from copy) and ask > politely to continue a discussion there? I tried it several times but > sometimes it happened that discussion was "forked” and continued in tw

Re: User-related questions in dev@ list

On Wed, Mar 10, 2021 at 11:16 AM Alexey Romanenko wrote: > > > What do you think should be the right behaviour for managing such emails? >> Forward this email to user@ (and remove dev@ address from copy) and ask >> politely to continue a discussion there? I tried it several times but >> sometimes

Re: User-related questions in dev@ list

As a frequent emailer of dev@, I'll admit that it's often very difficult to figure out if I should be emailing user@ or dev@, and typically just chose dev@ because it seems more likely to get an answer there. Having clearer guidelines around what is a "dev" topic would be very useful to better gui

Re: User-related questions in dev@ list

One of the sample mails belongs to me, sorry for that. I thought the dev list was a better place. Will ask similar to the other list as well. On Wed, Mar 10, 2021 at 12:13 PM Steve Niemitz wrote: > As a frequent emailer of dev@, I'll admit that it's often very difficult > to figure out if I shou

Re: User-related questions in dev@ list

I subscribed to both user@ and dev@. It seems to me that we have more active folks who have knowledge to offer help on the dev@ than the user@. It's always good to have dev@ and user@ for different usages as long as dev@ and user@ are almost equivalent helpful for dev/users to look for help. On We

Re: User-related questions in dev@ list

> On 10 Mar 2021, at 22:13, Onur Ozer wrote: > > One of the sample mails belongs to me, sorry for that. I thought the dev list > was a better place. Will ask similar to the other list as well. Onur, Well, I just picked up a random example of one of the latest emails, that, I believe, should b

Re: User-related questions in dev@ list

Note on the data: dev@ is much higher volume than user@ right now (maybe 2x?). [1] [2] I think https://beam.apache.org/community/contact-us/ has an OK description. I guess we could make it more clear about "Developer and contributor discussions" / "Developer mailing list" to mean that it is about

Re: User-related questions in dev@ list

My impression is that Boyuan is right: People may email dev@ because they may feel they're more likely to get a response. I'll confess that I am subscribed to both, but pay more attention to dev : / On Wed, Mar 10, 2021 at 2:16 PM Kenneth Knowles wrote: > Note on the data: dev@ is much higher vo

Re: User-related questions in dev@ list

I am in the same boat: I'm subscribed to both but the dev@ ones are more visible to me. That being said, I do think it's valuable to have segregated discussion (otherwise why have two lists), and "lurkers" on users@ can learn from questions answered there. I would say that it is on us to redirect

Re: User-related questions in dev@ list

> I would say that it is on us to redirect traffic to the correct place if we want to effect a change. +1 to this. I think the clean way to accomplish this is to say: "Let's continue this conversation on user@", add user@ and move dev@ to bcc (to avoid the fork), then (hopefully), answer the thr

Unexpected empty state address window set for ACTIVE window

Hello, We recently encountered an weird exception: Caused by: java.lang.IllegalStateException: Unexpected empty state address window set for ACTIVE window [2021-02-10T17:25:10.715Z..2021-02-10T20:25:10.715Z) at org.apache.beam.vendor.guava.v26_0_jre.com.google.common.base.Preconditions