Re: Disabling Jenkins Jobs

Nevermind, it was an issue with InfluxDB credentials that perhaps appeared during a transfer the workflows from Jenkins to GitHub actions. I fixed this. — Alexey > On 11 Dec 2023, at 17:56, Alexey Romanenko wrote: > > Hi, > > I’ve just noticed that some workflows stopped

Re: Disabling Jenkins Jobs

Hi, I’ve just noticed that some workflows stopped sending metrics to Grafana with an error “org.apache.beam.sdk.testutils.publishing.InfluxDBPublisher: Unable to publish metrics due to error: Response code: 401. Reason: "unable to parse authentication credentials”” (e.g. Nexmark, Tpcds). Is

Re: Embeddings generation in MLTransform

You need to send a blank email to dev-unsubscr...@beam.apache.org — Alexey > On 5 Dec 2023, at 11:57, Divya Sanghi wrote: > > Can someone suggest how to unsubscribe? > > On Mon, Oct 30, 2023 at 7:33 PM Anand Inguva via dev

Re: Implementing tuple type support in for ClickHouse connector

since Tuple is a nested type that can hold > any number of other ClickHouse types I was wondering what is the best type > from the Apache Beam side in order to implement it. > > Mark > > On Mon, Dec 4, 2023 at 12:24 PM Alexey Romanenko <mailto:aromanenko@gmail.com>>

Re: Implementing tuple type support in for ClickHouse connector

Hi Mark, What do you mean by “support” in this case? To map this ClickHouse data type to a Beam Schema data type as it’s done in org.apache.beam.sdk.io.clickhouse.TableSchema for other types or something else? — Alexey > On 3 Dec 2023, at 10:35, Mark Zitnik wrote: > > Hi Team, > > I am one

Re: Upgrading Avro dependencies

avro version with our current >> setup. >> >> John >> >> On Tue, Nov 14, 2023 at 4:20 PM Alexey Romanenko > <mailto:aromanenko@gmail.com>> wrote: >>> Thanks! Please, let me know if you need any help on this. >>> >>> — >

Re: Upgrading Avro dependencies

Thanks! Please, let me know if you need any help on this. — Alexey > On 14 Nov 2023, at 17:52, John Casey wrote: > > The vulnerability said to upgrade to 1.11.3, so I think that would be my > starting point. > > > On Mon, Nov 13, 2023 at 12:23 PM Alexey Romanenk

Re: Upgrading Avro dependencies

Alexey > > On Fri, Nov 10, 2023 at 12:53 PM Alexey Romanenko <mailto:aromanenko@gmail.com>> wrote: >> Hi John, >> >> This old Avro version in Beam is a very long story. Briefly, since initially >> it was toughly integrated into Java SDK “core” module then i

Re: Adding Dead Letter Queues to Beam IOs

Thanks a lot for working on this, long waiting and very demanded user feature. I’ll try to take a look on design doc in the next days. — Alexey > On 8 Nov 2023, at 21:43, John Casey via dev wrote: > > Hi All, > > I've written up a design for adding DLQs to existing Beam IOs. It's been >

Re: Upgrading Avro dependencies

Hi John, This old Avro version in Beam is a very long story. Briefly, since initially it was toughly integrated into Java SDK “core” module then it was not possible to upgrade an Avro version without breaking changes for users (because of some Avro incompatible changes, as you have noticed

Re: [VOTE] Release 2.52.0, release candidate #3

+1 (binding) Java SDK with Spark runner — Alexey > On 9 Nov 2023, at 16:44, Ritesh Ghorse via dev wrote: > > +1 (non-binding) > > Validated Python SDK quickstart batch and streaming. > > Thanks! > > On Thu, Nov 9, 2023 at 9:25 AM Jan Lukavský > wrote: >> +1

Re: Disabling Jenkins Jobs

s since the IO-Datastores cert is the problematic piece I think (and >> that has fixed a similar problem before). I'm not totally confident it will >> though given that the job succeeded last week. >> >> On Tue, Nov 7, 2023 at 10:18 AM Alexey Romanenko > <ma

Re: Disabling Jenkins Jobs

Not sure if it’s related but I see that, seems, all Jenkins jobs are stuck and there is a big Build Queue on https://ci-beam.apache.org/ Random clicks on jobs show that “"All nodes of label ‘beam’ are offline” message. Is it known problem? — Alexey > On 24 Oct 2023, at 21:50, Yi Hu via dev

Re: Processing time watermarks in KinesisIO

watermarks is completely decoupled and > unrelated, which I'd say is a bug. > > Jan > > [1] > https://beam.apache.org/releases/javadoc/current/org/apache/beam/sdk/io/kinesis/KinesisIO.Read.html#withProcessingTimeWatermarkPolicy-- > > On 10/27/23 16:51, Alexey Romanenko wr

Re: Processing time watermarks in KinesisIO

Why not just to create a custom watermark policy for that? Or you mean to make it as a default policy? — Alexey > On 27 Oct 2023, at 10:25, Jan Lukavský wrote: > > > Hi, > > when discussing about [1] we found out, that the issue is actually caused by > processing time watermarks in

Re: [NOTICE] Deprecation Avro classes in "core" and use "extensions/avro" instead for Java SDK

/beam/pull/27851/ > On 22 Feb 2023, at 20:21, Robert Bradshaw via dev wrote: > > Thanks for pushing this through! > > On Wed, Feb 22, 2023 at 10:38 AM Alexey Romanenko > wrote: >> >> Hi all, >> >> As a part of migration the Avro-related classes from

Re: Disabling Jenkins Jobs

Thanks for moving this forward! On a flip side, I noticed that many PreCommit actions (actually all for my PR #27851) are stuck waiting for a runner. Is it expected behaviour? Should we increase a number a runners while moving all Jenkins Jobs to GitHub actions? — Alexey > On 13 Oct 2023,

Re: [DISCUSS] Drop Euphoria extension

Can we just deprecate it for a while and then remove completely? — Alexey > On 13 Oct 2023, at 18:59, Jan Lukavský wrote: > > Hi, > > it has been some time since Euphoria extension [1] has been adopted by Beam > as a possible "Java 8 API". Beam has evolved from that time a lot, the >

Re: [VOTE] Release 2.51.0, release candidate #1

+1 (binding) — Alexey > On 5 Oct 2023, at 18:38, Jean-Baptiste Onofré wrote: > > +1 (binding) > > Thanks ! > Regards > JB > > On Tue, Oct 3, 2023 at 7:58 PM Kenneth Knowles wrote: >> >> Hi everyone, >> >> Please review and vote on the release candidate #1 for the version 2.51.0, >> as

Re: [ANNOUNCE] New PMC Member: Alex Van Boxel

Congrats Alex, very well deserved! — Alexey > On 4 Oct 2023, at 00:38, Austin Bennett wrote: > > Thanks for all you do, @Alex Van Boxel ! > > On Tue, Oct 3, 2023 at 12:50 PM Ahmed Abualsaud via dev > wrote: >> Congratulations! >>

Re: [ANNOUNCE] New PMC Member: Robert Burke

Congrats Robert, very well deserved! — Alexey > On 4 Oct 2023, at 00:39, Austin Bennett wrote: > > Thanks for all you do @Robert Burke ! > > On Tue, Oct 3, 2023 at 12:53 PM Ahmed Abualsaud > wrote: >> Congrats Rebo! >> >> On

Re: [ANNOUNCE] New PMC Member: Valentyn Tymofieiev

Congrats Valentyn, very well deserved! — Alexey > On 4 Oct 2023, at 00:39, Austin Bennett wrote: > > Thanks for everything @Valentyn Tymofieiev ! > > On Tue, Oct 3, 2023 at 12:53 PM Ahmed Abualsaud > wrote: >> Congrats

Re: User-facing website vs. contributor-facing website

AFAIR, the main point to use Wiki last time was a lower entry bar, comparing to the main website, for everybody to add a new information related to any of aspects of Beam. On the flip side, as it was mentioned above, this information is mostly not reviewed, bad structured and not easy to find

Re: Contribution of Asgarde: Error Handling for Beam?

I agree with Cham on these two options. In the end, it would be great to have such functionality (error handling / DLQ) integrated into Beam core API, but it will require, for sure, some technical discussions and reviews before - so it will take more time. Though, to make it available for

Re: [Discuss] Get rid of OWNERS files

I’m generally agree with this (initially that was a good intention imho) but what could be an alternative for this? Review bot also may assign reviewers that are no longer active on the project. — Alexey > On 8 Aug 2023, at 16:55, Danny McCormick via dev wrote: > > Hey everyone, I'd like to

Re: [VOTE] Release 2.49.0, release candidate #1

+1 (binding) Tested with https://github.com/Talend/beam-samples/actions (Java SDK v8/v11/v17, Spark 3.x runner). — Alexey > On 6 Jul 2023, at 17:34, Yi Hu via dev wrote: > > Hi everyone, > Please review and vote on the release candidate #1 for the version 2.49.0, as > follows: > [ ] +1,

Re: [DISCUSS] Enable Github Discussions?

-1 I understand that for some people, who maybe are not very familiar with ASF and its “Apache Way” [1], it may sound a bit obsolete but mailing lists are one of the key things of every ASF project which Apache Beam is. Having user@, dev@ and commits@ lists are required for ASF project to

Re: [VOTE] Release 2.48.0 release candidate #2

+1 (binding) Tested with https://github.com/Talend/beam-samples/ (Java SDK v8/v11/v17, Spark 3.x runner). > On 27 May 2023, at 19:38, Bruno Volpato via dev wrote: > > I was able to check that containers are all there and complete my validation. > > +1 (non-binding). > > Tested with

Re: Beam SQL found limitations

Hi Piotr, Thanks for details! I cross-post this to dev@ as well since, I guess, people there can provide more insights on this. A while ago, I faced the similar issues trying to run Beam SQL against TPC-DS benchmark. We had a discussion around that [1], please, take a look since it can be

Re: Repository Deletion Postmortem

Thanks for follow-up on this, it should be helpful. > The git revert command was used to create a revert commit. However, the > created commit deleted the entire repository. Do you have an idea what was a command and how it could deleted the entire repository? I’m asking about this to find a

Re: [VOTE] Release 2.47.0, release candidate #1

+1 (binding) Tested with https://github.com/Talend/beam-samples/ (Java SDK v8/v11/v17, Spark 3.x runner). --- Alexey > On 28 Apr 2023, at 16:06, Jack McCluskey via dev wrote: > > There was a GCP outage that impacted pushing containers to GCR, I expected it > to impact Java containers

Re: [ANNOUNCE] New committer: Anand Inguva

Congratulations, Anand! Well deserved! > On 25 Apr 2023, at 06:02, Byron Ellis via dev wrote: > > Congrats Anand! > > On Mon, Apr 24, 2023 at 9:54 AM Ahmet Altay via dev > wrote: >> Congratulations Anand! >> >> On Mon, Apr 24, 2023 at 8:05 AM Kerry Donny-Clark via

Re: [ANNOUNCE] New committer: Damon Douglas

Congratulations, Damon! Well deserved! > On 25 Apr 2023, at 09:17, Jan Lukavský wrote: > > Congrats Damon! > > On 4/25/23 06:15, Alex Kosolapov wrote: >> Congratulations, Damon! >> >> >> From: Kenneth Knowles >> Reply-To: "dev@beam.apache.org"

Re: [DISCUSS] @Experimental, @Internal, @Stable, etc annotations

gt;>>>>> 2. It has an unintended effect (making users afraid to use things >>>>>>> which they should be happy to use) >>>>>>> 3. We don't use it consistently (many less-safe things are not >>>>>>> experi

Re: [DISCUSS] @Experimental, @Internal, @Stable, etc annotations

Great and long-to-wait topic to discuss. My personal opinion based on what I saw on different open-source projects is that all such annotations, like @Experimental or @Stable, are not usefull along the time and even rather useless and misleading. What actually play roles is artifacts

Re: Error debezium

Hi Juan Manuel montoya, Thanks for working on this! Just for reference - all Beam Java artifacts are normally built with Java 8 but they are tested and suposed to work with Java 11 and Java 17. Also, it would be great to track a progress on this work for Debezium integration by creating a

Re: [VOTE] Release 2.46.0, release candidate #1

+1 (binding) Tested with https://github.com/Talend/beam-samples/ (Java SDK v8/v11/v17, Spark 3.x runner). --- Alexey > On 7 Mar 2023, at 07:38, Ahmet Altay via dev wrote: > > +1 (binding) - I validated python quickstarts on direct & dataflow runners. > > Thank you for doing the release! >

[NOTICE] Deprecation Avro classes in "core" and use "extensions/avro" instead for Java SDK

Hi all, As a part of migration the Avro-related classes from Java SDK “core” module to a dedicated extension [1] (as it was discussed here [2] and here [3]), two important PRs has been merged [4][5]. Therefore, old Avro-related classes became deprecated in “core” (still possible to use but not

Re: Broken Jenkins jobs

Thanks for taking care of this, Yi! — Alexey > On 20 Feb 2023, at 20:21, Yi Hu via dev wrote: > > Hi Alexy, > > Thanks for raising this. The breaking change is found: > https://github.com/apache/beam/pull/25566 > > Best, > Yi > > On Mon, Feb 20,

Broken Jenkins jobs

Hi all, Jenkins jobs “beam_PreCommit_SQL_Java11_Commit” [1] and “beam_PreCommit_SQL_Java17_Commit” [2] seems are broken since Feb 17th. Anyone is looking into this ? — Alexey [1] https://ci-beam.apache.org/job/beam_PreCommit_SQL_Java11_Commit/ [2]

[ANNOUNCE] New PMC Member: Jan Lukavský

Hi all, Please join me and the rest of the Beam PMC in welcoming Jan Lukavský as our newest PMC member. Jan has been a part of Beam community and a long time contributor since 2018 in many significant ways, including code contributions in different areas, participating in technical

Re: [VOTE] Release 2.45.0, Release Candidate #1

+1 (binding) Tested with https://github.com/Talend/beam-samples/ (Java SDK v8/v11/v17, Spark 3.x runner). --- Alexey > On 13 Feb 2023, at 17:54, Ahmet Altay via dev wrote: > > +1 (binding) - I validated python quick starts on direct runner and python > streaming quickstart on dataflow. >

Re: [BEAM-13261] PR review needed

Thanks, I’ll take a look — Alexey > On 14 Jan 2023, at 10:38, Piyush Sagar wrote: > > Hello Beam Devs, > > Requesting a review for a PR: https://github.com/apache/beam/pull/24851 and > Task: https://github.com/apache/beam/issues/21200 > > Thanks >

Re: [VOTE] Release 2.44.0, release candidate #1

+1 (binding) Tested with https://github.com/Talend/beam-samples/ (Java SDK v8/v11/v17, Spark 3 runner). --- Alexey > On 11 Jan 2023, at 16:53, Ritesh Ghorse via dev wrote: > > +1 (non-binding) > Validated Go Dataframe Transform wrapper on Dataflow runner and Go SDK > quickstart on Direct

Re: How to write an IO guide draft

I doubt that it will be a "de-facto" standard behaviour for all runners in the short term until the cross-language funtionality brings additional complexity into pipeline deployment and performance overhead. Perhaps, it will be changed in long term, but for now, I may guess that the most of

Re: Beam Website Feedback

Always happy to help! Many thanks for your work to make Beam website better! — Alexey > On 6 Jan 2023, at 21:54, Alex Kosolapov wrote: > > Thank you, Ahmet! Happy to help! Both changes [1] and [2] have been reviewed > and merged by Alexey Romanenko. > > We wanted to than

Re: [DISCUSS] Avro dependency update, design doc

github.com/apache/beam/issues/24292 [3] https://github.com/apache/beam/issues/24293 — Alexey > On 18 Nov 2022, at 15:56, Alexey Romanenko wrote: > > Since there are no principal objections against the proposed option 2 > (extract Avro-related code from “core” to Avro extension b

Re: Beam Website Feedback

ted a PR to update the website > (https://github.com/apache/beam/pull/24733). I do not know if that is the > best solution. As an alternative we could consider setting up a redirect for > the old link. We do not know who else would be still linking to the old one. > > Ahmet > >

Re: Beam Website Feedback

Hi Rajkumar, Could you specify where (which page) this link was found? Thanks! — Alexey > On 20 Dec 2022, at 10:08, Rajkumar Gupta via dev wrote: > > Hi Team, > > Just a minor point, while browsing the site I noticed that the link below is > not working. Can you please check? >

Re: [Proposal] Adopt a Beam I/O Standard

> The associated docs are: >>> https://s.apache.org/beam-io-api-standard-documentation >>> https://s.apache.org/beam-io-api-standard >>> >>> This is missing all the relational stuff that was in those docs, this >>> appears to be another attempt start

Re: [Proposal] | Move FileIO and TextIO from :sdks:java:core to :sdks:java:io:file

On 12 Dec 2022, at 22:23, Robert Bradshaw via dev wrote: > > Saving up all the breaking changes until a major release definitely > has its downsides (look at Python 3). The migration path is often as > important (if not more so) than the final destination. Actually, it proves that the major

Re: [Proposal] Adopt a Beam I/O Standard

Thanks for writing this! IIRC, the similar design doc was sent for review here a while ago. Is this just an updated version and a new one? — Alexey > On 11 Dec 2022, at 15:16, Herman Mak via dev wrote: > > Hello Everyone, > > *TLDR* > > Should we adopt a set of standards that Connector

Re: Issue with website update and Jenkins

Thanks, Kenn! > On 30 Nov 2022, at 18:59, Kenneth Knowles wrote: > > I filed https://issues.apache.org/jira/browse/INFRA-23967 > > On Tue, Nov 29, 2022 at 7:53 AM Alexey Romanenko <mailto:aromanenko@gmail.com>> wrote: >> It looks that

Re: [DISCUSSION][JAVA] Current state of Java 17 support

e do >> ]? I am not certain on whether this would only be critical for releases, or >> should be done as part of regular CI. >> >> On Tue, Nov 29, 2022 at 8:51 AM Alexey Romanenko > <mailto:aromanenko@gmail.com>> wrote: >>> Hello, >>>

Re: Issue with website update and Jenkins

t 10, 2022 at 8:18 AM Alexey Romanenko <mailto:aromanenko@gmail.com>> wrote: >> The issue is resolved. >> Thank you to everybody who made this working again! >> >> --- >> Alexey >> >>> On 7 Oct 2022, at 15:26, Alexey Roma

[DISCUSSION][JAVA] Current state of Java 17 support

Hello, I’m sorry if it’s already discussed somewhere but I find myself a little bit lost in the subject. So, I’d like to clarify this - what is a current official state of Java 17 support at Beam? I recall that a great job was done to make Beam compatible with Java 17 [1] and Beam already

Re: Beam, Flink state and Avro Schema Evolution is problematic

+ dev Many thanks for sharing your observations and findings on this topic, Cristian! I copy it to dev@ as well to attract more attention to this problem. — Alexey > On 18 Nov 2022, at 18:21, Cristian Constantinescu wrote: > > Hi everyone, > > I'm using Beam on Flink with Avro generated

Re: [DISCUSS] Avro dependency update, design doc

; core) seems best. I think +Reuven Lax might have the most context on any >> technical issue we will >> >> Thank you for writing this document. It really helps to understand the >> options. I agree that option 2 (make a new extension and deprecate from >&g

Re: [VOTE] Release 2.43.0, release candidate #2

+1 (binding) — Alexey > On 15 Nov 2022, at 14:37, Ritesh Ghorse via dev wrote: > > +1 (non-binding) > > Validated Go SDK quickstart on Direct and Dataflow runner. Also validated > Dataframe wrapper on Portable and Dataflow runner. > > > On Tue, Nov 15, 2022 at 5:17 AM Anand Inguva via dev

Re: bhulette stepping back (for now)

Hey Brian, Many thanks for your contributions! Good luck with your new adventure! — Alexey > On 12 Nov 2022, at 20:47, Chamikara Jayalath via dev > wrote: > > Good luck with your next endeavor Brian! Thanks for all the contributions to > Beam (and hopefully more in the future when you have

Re: [ANNOUNCE] New committer: Yi Hu

Congratulations! Well deserved! — Alexey > On 9 Nov 2022, at 21:01, Tomo Suzuki via dev wrote: > > Congratulations! > > On Wed, Nov 9, 2022 at 3:00 PM John Casey via dev > wrote: >> Congrats! this is well deserved YI >> >> On Wed, Nov 9, 2022 at 2:58 PM Austin

Re: [DISCUSS] Avro dependency update, design doc

rwardly - I am concerned of what could go wrong for users in the > in-between/transition state while more slowly transitioning avro to extension. > > On Wed, Nov 9, 2022 at 5:43 AM Alexey Romanenko <mailto:aromanenko@gmail.com>> wrote: >> Any thoughts on this? For now,

Re: [DISCUSS] Avro dependency update, design doc

Any thoughts on this? For now, we'd need to decide which path finally to take to move forward. Thanks in advance! — Alexey > On 4 Nov 2022, at 16:44, Alexey Romanenko wrote: > > Hi all, > > Following-up an Avro dependency update discussion [1] that showed a lot of > unc

Re: [VOTE] Release 2.43.0, release candidate #1

+1 (binding) Tested with https://github.com/Talend/beam-samples/ (Java SDK v8 & v11, Spark 3 runner). --- Alexey > On 9 Nov 2022, at 01:38, Chamikara Jayalath via dev > wrote: > > Hi everyone, > Please review and vote on the release candidate #1

[DISCUSS] Avro dependency update, design doc

Hi all, Following-up an Avro dependency update discussion [1] that showed a lot of uncertainties to move forward, Moritz and I decided to create a design document [2] with potential options, that we believe, can be considered and used further. Unfortunately, all solutions lead to breaking

Re: [PROPOSAL] Re-enable checkerframework by default

+1 to make it “on" by default with mentioning that on Contribution Guide. I recall for one PR that it took me some time to realise why it was failing on Jenkins and not locally because of this different behaviour. — Alexey > On 20 Oct 2022, at 00:51, Kenneth Knowles wrote: > > Hi all, > >

Re: [VOTE] Release 2.42.0, release candidate #2

+1 (binding) Tested with https://github.com/Talend/beam-samples/ (Java SDK v8 & v11, Spark 3 runner). --- Alexey > On 14 Oct 2022, at 05:17, Ahmet Altay via dev wrote: > > +1 (binding) > > Tested python quickstart examples on the direct runner.

Re: Issue with website update and Jenkins

The issue is resolved. Thank you to everybody who made this working again! --- Alexey > On 7 Oct 2022, at 15:26, Alexey Romanenko wrote: > > Hi everybody, > > The is an issue with updating a content on Beam website. I believe it’s > caused by not running the Jenkins

Issue with website update and Jenkins

Hi everybody, The is an issue with updating a content on Beam website. I believe it’s caused by not running the Jenkins job that publishes the Beam website into the asf-site branch since 30 Sep 2022 [1] with an error message “There are no nodes with the label ‘git-websites’”: -

Re: [VOTE] Release 2.42.0, release candidate #1

Is it a regression or just recently discovered? — Alexey > On 6 Oct 2022, at 01:13, Eike Falkenberg via dev wrote: > > Hey everyone, > > We have gotten customer feedback about by this issue > and provided a PR that is in > review

Re: Beam Website Feedback

Thanks for your feedback. At the time, using a Google website search was a simplest solution since, before, we didn’t have a search at all. I agree that it could be frustrating to have ad links before the actual results (not sure that we can avoid them there) but "it is what it is” and it's

Re: [VOTE] Release 2.42.0, release candidate #1

+1 (binding) Tested with https://github.com/Talend/beam-samples/ (Java SDK v8 & v11, Spark 3 runner). --- Alexey > On 3 Oct 2022, at 14:32, Chamikara Jayalath via dev > wrote: > > +1 (binding) > > Verified checksums and

Re: Performance and Cost benchmarking

Thanks for raising this topic. > On 26 Sep 2022, at 23:32, Andrew Pilloud via dev wrote: > > I left some comments on your design. Your doc discusses a bunch of > details about infrastructure such as testing frameworks, automation, > and performance databases, but doesn't describe how it will

[ANNOUNCE][Testing] TPC-DS benchmark suite in Beam

Hi everybody, As some of you may know, at Talend, we’ve been working for a while to add TPC-DS benchmark suite into Beam. We believe that having TPC-DS as a part of Beam testing workflow and release routine will help a community to detect quickly the performance regressions or improvements,

Re: Beam Dependency Check Report (2022-09-15)

Is it a bug that this email is empty? > On 15 Sep 2022, at 19:40, Apache Jenkins Server > wrote: >

Re: [Infrastructure] Periodically run Java microbenchmarks on Jenkins

he job to 'beam-perf' to use it. For > example: > https://github.com/apache/beam/blob/66bbee84ed477d86008905646e68b100591b6f78/.test-infra/jenkins/job_PostCommit_Java_Nexmark_Direct.groovy#L36 > > Andrew > > On Wed, Sep 14, 2022 at 8:28 AM Alexey Romanenko > wrote: >&

Re: [Infrastructure] Periodically run Java microbenchmarks on Jenkins

I think it depends on the goal why to run that benchmarks. In ideal case, we need to run them on the same dedicated machine(s) and with the same configuration all the time but I’m not sure that it can be achieved in current infrastructure reality. On the other hand, IIRC, the initial goal of

Re: [VOTE] Release 2.41.0, release candidate #2

+1 (binding) I tested it with https://github.com/Talend/beam-samples/ - no byte_buddy issue for now. (Java SDK v8 & v11, Spark 3 runner). --- Alexey > On 19 Aug 2022, at 10:40, Jan Lukavský wrote: > > +1 (non-binding) > > Validated Java SDK

Re: [VOTE] Release 2.41.0, release candidate #1

Just for reference: it looks that it happens only with default package classes [1]. [1] https://github.com/raphw/byte-buddy/issues/1301#issuecomment-1218475514 > On 18 Aug 2022, at 12:40, Alexey Romanenko wrote: > > >> On 17 Aug 2022, at 22:52, Kenneth Knowles > <m

Re: [VOTE] Release 2.41.0, release candidate #1

> On 17 Aug 2022, at 22:52, Kenneth Knowles wrote: > > Seems like there has been a lot of progress on > https://github.com/raphw/byte-buddy/issues/1301 > . Since it has been > identified, I think we can be pretty confident that the version

Re: [VOTE] Release 2.41.0, release candidate #1

sion? — Alexey > Kenn > > On Tue, Aug 16, 2022 at 12:50 PM Kiley Sok via dev <mailto:dev@beam.apache.org>> wrote: > cc: @Liam Miller-Cushon <mailto:cus...@google.com>, who worked on the > bytebuddy update. > > Liam, do you have any context on this

Re: Forward StackOverflow questions with the apache-beam tag to a new mailing list

Good point about unanswered SO questions. +1 that we need to improve a situation there. Yes, we may try to stream them to a new dedicated list but it will require people here to subscribe to and check regularly one more list which perhaps won’t be so efficient as well. I believe that a

Re: [VOTE] Release 2.41.0, release candidate #1

I tested with "beam-samples" [1] and found that a rather simple test pipeline fails [2] with this runtime error: Error: Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.776 s <<< FAILURE! - in SerializationTest 5809 Error: SerializationTest.nonSerilizableTest Time

Re: Runner benchmarks in portable mode

AFAIK, in Beam, we don’t have any “official” benchmarks or load tests that are running with any of portable runners. It would be a great improvement if we would have them. — Alexey > On 28 Jul 2022, at 19:30, Bharath Kumara Subramanian > wrote: > > Hi, > > We are currently working on

Re: [PROPOSAL] Stop Spark2 support in Spark Runner

ed looking into the Spark runner code a bit to helpfully help > supporting it. > Besides having to maintain (test!) twice the number of artifacts, there’s > also a significant negative impact on developer ergonomics / productivity > supporting multiple major versions (separate modules to de

Re: Jira -> GitHub Issues Migration (This Friday)

I also haven't been around the project for as long >> and didn't previously build that feature into my regular workflow - others >> might find it more useful. >> >> Thanks, >> Danny >> >> On Fri, Jun 24, 2022 at 1:30 PM Alexey Romanenko >> wrote: &

Re: [DISCUSS] What to do about P0/P1/flake automation Was: P1 issues report (70)

Thanks, Danny! > On 24 Jun 2022, at 19:23, Danny McCormick wrote: > > Sure, I put up a fix - https://github.com/apache/beam/pull/22048 > <https://github.com/apache/beam/pull/22048> > On Fri, Jun 24, 2022 at 1:20 PM Alexey Romanenko <mailto:aromanenko@gmail.c

Re: Jira -> GitHub Issues Migration (This Friday)

escribió: > Given the consensus here, I updated the tool to do this. This means that we > won't update the JIRAs to be read-only until after the migration is complete. > I'll rerun the tool if any extra jiras come in during the intervening period. > The tool will als

Re: [DISCUSS] What to do about P0/P1/flake automation Was: P1 issues report (70)

> > 2. The links in this report start with api.github.* and don’t take us > > directly to the issues. > > > Yeah Danny pointed that out as well. I'm assuming he knows how to fix it? > > This is already fixed - Pablo actually beat me to it! > It

Re: [VOTE] Release 2.40.0, candidate #2

+1 (binding) The same testing as for RC1 — Alexey > On 24 Jun 2022, at 05:51, Pablo Estrada wrote: > > +1 (binding) > > I've tested by building and running local tests for existing Dataflow > Templates. > > On Thu, Jun 23, 2022 at 2:39 PM Pablo Estrada > wrote: >

Re: [VOTE] Release 2.40.0, candidate #1

+1 (binding) I tested it with https://github.com/Talend/beam-samples/ (Java 8&11 SDK, Spark 3 runner). --- Alexey > On 21 Jun 2022, at 04:28, Ahmet Altay wrote: > > > > On Mon, Jun 20, 2022 at 6:35 PM Pablo Estrada >

Re: Jenkins CI currently unavailable

Additionally to what Kenn said, we have some documentation here: https://cwiki.apache.org/confluence/display/BEAM/Jenkins+Tips Though, not sure how up-to-date it is. — Alexey > On 14 Jun 2022, at 16:42, Kenneth Knowles wrote: >

Re: Failing beam_SeedJob

apache.org/jira/browse/BEAM-14377 > <https://issues.apache.org/jira/browse/BEAM-14377> but Pablo's changes were > rolled back because somehow seed job became broken. > > On Fri, Jun 3, 2022 at 2:56 PM Alexey Romanenko <mailto:aromanenko@gmail.com>> wrote: > Yes,

Re: Failing beam_SeedJob

nd May 19 > to this infrastructure. Hoping INFRA can help us sort it out. > > Kenn > > On Thu, Jun 2, 2022 at 9:15 AM Alexey Romanenko <mailto:aromanenko@gmail.com>> wrote: > Thanks Ahmet and Ryan for taking a look! > > I agree that referenced commits seems are not r

Re: Jira -> GitHub Issues Migration (This Friday)

+1 That would be very helpful for mapping! > On 2 Jun 2022, at 17:48, Ahmet Altay wrote: > > Is it possible to add comments on the JIRAs with a link to the new > corresponding github issue? > > On Thu, Jun 2, 2022 at 8:47 AM Danny McCormick > wrote: > Thanks

Re: Failing beam_SeedJob

ry that. We may need to ask infra. > ( @Ryan Thompson <mailto:ryanthomp...@google.com> - could you please infra to > restart jenkins?) > > I do not think this issue is related to any change in the source control. The > commit referenced in the first failed job is an unrelated doc

Re: Failing beam_SeedJob

May 2022, at 17:08, Alexey Romanenko wrote: > > The first failed job is https://ci-beam.apache.org/job/beam_SeedJob/9696/ > <https://ci-beam.apache.org/job/beam_SeedJob/9696/> > It fails with this error (that says not so much): > > Processing DSL script .test-infra/jenkin

Re: [CDAP IO] Failing R JavaPrecommit checks

I guess it’s related to added a hard version of scala-library dependency. Try to make it “compileOnly” (as we do for Spark runner for example). Also, there is no need to escalate it to BeamModulePlugin.groovy - please, keep it local for your module. — Alexey > On 31 May 2022, at 23:17,

Re: [ANNOUNCE] New committer: Ke Wu

Congrats, Ke! — Alexey > On 31 May 2022, at 18:09, Xinyu Liu wrote: > > Congrats! > > Xinyu > > On Mon, May 30, 2022 at 7:46 AM Evan Galpin > wrote: > Congrats Ke! > > - Evan > > > On Mon, May 30, 2022 at 4:11 AM Jan Lukavský > wrote: >

Re: Failing beam_SeedJob

May 2022, at 16:24, Alexey Romanenko wrote: > > Hi everyone, > > Jenkins job `beam_SeedJob` keeps failing starting from May 19th. The last > successful build [2] was 12 days ago. > Does anyone know the reasons of this? > > — > Alexey > > > [1] https://ci-bea

  1   2   3   4   5   6   >