You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by "scott-strong (via GitHub)" <gi...@apache.org> on 2024/01/08 18:10:57 UTC

[I] [Feature Request]: Differentiate between batchSize and minBatchSize in JDBCIO Write [beam]

scott-strong opened a new issue, #29955:
URL: https://github.com/apache/beam/issues/29955

   ### What would you like to happen?
   
   Prior to release 2.37.0, setting the `batchSize` indicated that a batch would consist of at least that many records if executed prior to the window duration. After the release of 2.37.0, `batchSize` instead became the minimum batch size, meaning that if the elements in the given bundle did not exceed the set `batchSize`, the elements would be executed immediately rather than collected to be executed once the `batchSize` was reached.
   
   This has caused issues in pipelines where more frequent writes are causing more deadlocks/lock wait timeouts. The problem then gets exacerbated as backlog grows and workers are added.
   
   I'm proposing that we have a way to at least differentiate between these two batching strategies to allow for batches to build up rather than execute with a very small number of elements.
   
   ### Issue Priority
   
   Priority: 2 (default / most feature requests should be filed as P2)
   
   ### Issue Components
   
   - [ ] Component: Python SDK
   - [X] Component: Java SDK
   - [ ] Component: Go SDK
   - [ ] Component: Typescript SDK
   - [ ] Component: IO connector
   - [ ] Component: Beam YAML
   - [ ] Component: Beam examples
   - [ ] Component: Beam playground
   - [ ] Component: Beam katas
   - [ ] Component: Website
   - [ ] Component: Spark Runner
   - [ ] Component: Flink Runner
   - [ ] Component: Samza Runner
   - [ ] Component: Twister2 Runner
   - [ ] Component: Hazelcast Jet Runner
   - [ ] Component: Google Cloud Dataflow Runner


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Feature Request]: Differentiate between batchSize and minBatchSize in JDBCIO Write [beam]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #29955: [Feature Request]: Differentiate between batchSize and minBatchSize in JDBCIO Write
URL: https://github.com/apache/beam/issues/29955


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Feature Request]: Differentiate between batchSize and minBatchSize in JDBCIO Write [beam]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #29955:
URL: https://github.com/apache/beam/issues/29955#issuecomment-4388334552

   This issue has been closed due to lack of activity. If you think that is incorrect, you can reopen the issue at any time.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] [Feature Request]: Differentiate between batchSize and minBatchSize in JDBCIO Write [beam]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #29955:
URL: https://github.com/apache/beam/issues/29955#issuecomment-4192331517

   This issue has been marked as stale due to 150 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that’s incorrect or this issue still needs to be addressed, please simply write any comment. If closed, you can reopen the issue at any time. Thank you for your contributions.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org