Skip to content

Continue calling S3SinkService::output even if records is empty to flush stale batches #6539

Continue calling S3SinkService::output even if records is empty to flush stale batches

Continue calling S3SinkService::output even if records is empty to flush stale batches #6539

Triggered via pull request August 17, 2023 22:19
Status Success
Total duration 8m 58s
Artifacts
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
build (17, 0.9.0-alpha)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (11, 0.9.0-alpha)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (17, 0.16.0-alpha)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (11, 0.16.0-alpha)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/