Hi Alex,
My problem trying to locally run that test was that, since I don't have
access to the apache-beam-testing GCP project I was having problems getting
a datastore instance to read/write from.
On Tue, Aug 10, 2021 at 1:08 PM Alex Amato wrote:
> Miguel, I believe you were having trouble
>
> It is likely that the incorrect transform was edited...
>
It appears you're right; I tried to reproduce but this time was able to
clear the issue by making "the same" code change and updating the
pipeline. I believe it was just a change in the wrong place in code.
Good to know this works!
Thanks!
On 10 Aug 2021, at 18:21, Luke Cwik mailto:lc...@google.com>>
wrote:
Welcome.
I have granted you the access you requested.
Please take a look at the contribution guide[1] as it helps answer many
questions.
1: https://beam.apache.org/contribute/
On Tue, Aug 10, 2021 at 10:06 AM
This is your daily summary of Beam's current flaky tests
(https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20statusCategory%20!%3D%20Done%20AND%20labels%20%3D%20flake)
These are P1 issues because they have a major negative impact on the community
and make it hard to
I’ve made a bad job of the PR, I’m really sorry. This is my proposed commit:
https://github.com/apache/beam/pull/15306/commits/0f5324321aea01ea035a6e9c46dc80faf1b078f5
On 10 Aug 2021, at 18:15, Reuven Lax
mailto:re...@google.com>> wrote:
Definitely happy to look at a PR.
On Tue, Aug 10, 2021
This is your daily summary of Beam's current P1 issues, not including flaky
tests
(https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20statusCategory%20!%3D%20Done%20AND%20priority%20%3D%20P1%20AND%20(labels%20is%20EMPTY%20OR%20labels%20!%3D%20flake).
See
This is your daily summary of Beam's current outages. See
https://beam.apache.org/contribute/jira-priorities/#p0-outage for the meaning
and expectations around P0 issues.
BEAM-12723: beam_PreCommit_Java_Examples_Dataflow_Phrase failing due to key
negotiation error
I created an issue for this: https://issues.apache.org/jira/browse/BEAM-12736
I also took a stab at a fix. Would you accept a pull request? Or, I'd be happy
to discuss.
Cheers,
Chris.
On 9 Aug 2021, at 21:02, Chris Hinds
mailto:chris.hi...@bdi.ox.ac.uk>> wrote:
Haha, it probably shouldn’t!
Thanks for your responses Luke. One point I have confusion over:
* Modify the sink implementation to do what you want with the bad data and
> update the pipeline.
>
I modified the sink implementation to ignore the specific error that was
the problem and updated the pipeline. The update
Hello,
I’ve been dipping in an out of Beam as a user for a while. I came across an
issue and I’d like to assign it to myself (username: chrishinds).
Thanks!
Chris.
Hi all,
I recently had an experience where a streaming pipeline became "clogged"
due to invalid data reaching the final step in my pipeline such that the
data was causing a non-transient error when writing to my Sink. Since the
job is a streaming job, the element (bundle) was continuously
Yeah, it totally works for me!
Thanks again
- Fer
On Mon, Aug 9, 2021 at 5:20 PM Pablo Estrada wrote:
> Hi Fernando,
> by any chance, could we make this 30 minutes earlier? A conflict came up
> that's a little hard to move.
>
> On Mon, Aug 9, 2021 at 8:03 AM Fernando Morales Martinez <
>
12 matches
Mail list logo