Use separate test sourcesets per avro version for generated Avro classes #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Merged

aromanenko-dev merged 1 commit into aromanenko-dev:avro_25215_multiple_versions from mosche:avro_25215_multiple_versions_source_sets

Mar 21, 2023

mosche commented Mar 21, 2023

Let's give this a try later @aromanenko-dev , i think it should work 🙏

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

Choose reviewer(s) and mention them in a comment (R: @username).
Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
If this contribution is large, please file an Apache Individual Contributor License Agreement.

Post-Commit Tests Status (on master branch)

Lang	SDK	Apex	Dataflow	Flink	Gearpump	Samza	Spark
Go		---	---		---	---
Java
Python		---			---	---
XLang	---	---	---		---	---	---

Pre-Commit Tests Status (on master branch)

---	Java	Python	Go	Website
Non-portable
Portable	---		---	---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.


          Use separate test sourcesets per avro version for generated Avro classes

1d2afde

aromanenko-dev merged commit 10105aa into aromanenko-dev:avro_25215_multiple_versions

mosche deleted the avro_25215_multiple_versions_source_sets branch

May 11, 2023 12:15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet