Repository navigation
sync with open source how - #118
Draft
lesterhaynes wants to merge 10000 commits into
Draft
lesterhaynes wants to merge 10000 commits into
lesterhaynes wants to merge 10000 commits into
Conversation
njeevan233-spec
approved these changes
Feb 1, 2026
![dependabot[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
Bumps [github.com/aws/aws-sdk-go-v2/service/s3](https://github.com/aws/aws-sdk-go-v2) from 1.114.6 to 1.114.8. - [Release notes](https://github.com/aws/aws-sdk-go-v2/releases) - [Commits](aws/aws-sdk-go-v2@service/s3/v1.114.6...service/s3/v1.114.8) --- updated-dependencies: - dependency-name: github.com/aws/aws-sdk-go-v2/service/s3 dependency-version: 1.114.8 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [github.com/testcontainers/testcontainers-go](https://github.com/testcontainers/testcontainers-go) from 0.44.0 to 0.45.0. - [Release notes](https://github.com/testcontainers/testcontainers-go/releases) - [Commits](testcontainers/testcontainers-go@v0.44.0...v0.45.0) --- updated-dependencies: - dependency-name: github.com/testcontainers/testcontainers-go dependency-version: 0.45.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [docker/login-action](https://github.com/docker/login-action) from 4.7.0 to 4.8.0. - [Release notes](https://github.com/docker/login-action/releases) - [Commits](docker/login-action@81c6f93...8aa5831) --- updated-dependencies: - dependency-name: docker/login-action dependency-version: 4.8.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [github/codeql-action](https://github.com/github/codeql-action) from 4.39.2 to 4.39.3. - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](github/codeql-action@v4.39.2...v4.39.3) --- updated-dependencies: - dependency-name: github/codeql-action dependency-version: 4.39.3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* [Solace] Fix flaky SolaceIO integration tests * [Solace] Pin the Solace precommit to the default Java version
* Retry transient errors in BigqueryClient.queryUnflattened queryUnflattened polled jobs.getQueryResults with no retry, so one 503 backendError failed an integration test after its pipeline had already succeeded. Poll through getQueryResultsWithRetries, which uses the same backoff as the other BigqueryClient methods. It retries 5xx and 429 and throws other 4xx errors right away. Also delete the temporary dataset in a finally block. Before, the method skipped the delete when the query returned no rows or threw. * Retry the whole query job in BigqueryClient.queryUnflattened Polling getQueryResults again can't fix a job that itself failed with a transient error such as a 503 backendError, because every poll returns the same error. Each retry now starts a new query job, which also covers a 503 from jobs.insert. The temp table uses WRITE_TRUNCATE so a retried job overwrites anything a failed job left behind. The retry check also treats 403 rateLimitExceeded as transient, applies the status-code rules to non-JSON HTTP errors, and keeps the original jobComplete check so a missing value fails instead of looping.
Bumps [cloud.google.com/go/pubsub](https://github.com/googleapis/google-cloud-go) from 1.51.1 to 1.52.0. - [Release notes](https://github.com/googleapis/google-cloud-go/releases) - [Changelog](https://github.com/googleapis/google-cloud-go/blob/main/documentai/CHANGES.md) - [Commits](googleapis/google-cloud-go@pubsub/v1.51.1...pubsub/v1.52.0) --- updated-dependencies: - dependency-name: cloud.google.com/go/pubsub dependency-version: 1.52.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [github.com/aws/aws-sdk-go-v2/feature/s3/manager](https://github.com/aws/aws-sdk-go-v2) from 1.23.19 to 1.23.21. - [Release notes](https://github.com/aws/aws-sdk-go-v2/releases) - [Commits](aws/aws-sdk-go-v2@service/pipes/v1.23.19...service/pipes/v1.23.21) --- updated-dependencies: - dependency-name: github.com/aws/aws-sdk-go-v2/feature/s3/manager dependency-version: 1.23.21 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Because otel follows semver, the API package is guarenteed until the next bump. This overly constrained version will require more churn to keep up to date, and make it difficult for users of the package to keep their deps up to date. https://opentelemetry.io/docs/specs/otel/versioning-and-stability/
…ingModelHandler (#41051)
…#40951) Declares ParDoFn.getDoFnInfo() to expose the DoFnInfo of underlying DoFn instances. Implements ParDoFn.getDoFnInfo() across worker ParDoFn implementations. Implements SimpleParDoFnHelpers.getDoFnInfo() to return activeFnInfo if currently processing a bundle, otherwise falling back to peeking at the DoFnInstanceManager. Updates SimpleParDoFn and StreamingKeyedWorkItemSideInputParDoFn to delegate getDoFnInfo() to SimpleParDoFnHelpers, removing the need for a separate getActiveDoFnInfo() testing method. Simplifies UserParDoFnFactoryTest to call parDoFn.getDoFnInfo() directly without casting.
* fix gib * address comments * format Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…) (#40926) Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* Port DatastoreV1Test off DoFnTester The fns under test hold Mockito mocks that can't be serialized, so TestPipeline doesn't fit. Add a small processBundle helper that runs the fn in-process through DoFnRunners.simpleRunner and use it at the 10 DoFnTester call sites. Fixes #18692 * Move FakeWriteBatcher Javadoc back above its class
…dow (#40611) * [Flink] Add a dedicated operator for batch combines in the global window In batch, the final step of GroupByKey and Combine runs Beam's general windowing machinery (WindowDoFnOperator with ReduceFnRunner). For each key it binds keyed state, watermark holds and pane info, sets a timer, fires it when the key changes and clears all state. In a profiled Scio batch job this bookkeeping was 30-40% of the reduce phase, against about 6% for merging the accumulators. Add a batch-only --sortedBatchCombine option, enabled by default (disable it with --sortedBatchCombine=false). In the global window with the default trigger and without side inputs, the final step then uses a SortedBatchCombineOperator. It relies on Flink feeding a keyed operator all records of a key together, combines them in plain fields, and emits the result when the key changes or the input ends. Watermarks are held back until the end of the input, and the last key is emitted before the final watermark is forwarded. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * [Flink] Say the sorted batch combine needs DataStream batch mode on Flink 1.x Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * [Flink] Test the default of the sorted batch combine option Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ds (#41107) Python always sends redistribute_num_keys, 0 by default, and the external builder copied it, so the default from withRedistribute() was never applied and the Redistribute created one key per record.
… cache miss (#41065) * Increase Gradle wrapper networkTimeout and retry wrapper bootstrap on cache miss * Add comment explaining Gradle wrapper cache-miss retry block
* add changes function * address comments and make iceberg cdc source respect the new convention * spotless * trigger ITs
…nManagement (#41118) * Configure mavenCentralMirrorUrl in buildSrc/settings.gradle.kts pluginManagement * Use fully-qualified java.util.Properties inside pluginManagement block * Consolidate Maven Central mirror logging to a single log line in settings.gradle.kts
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Please add a meaningful description for your change here
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>instead.CHANGES.mdwith noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI.