You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per the note "@deprecated with no replacement since 5.0, scheduled for removal in 6.0. Use a custom {@link RepeatOperations} implementation (based on a {@link TaskExecutor} with a bounded task queue) and set it on the step with {@link #stepOperations(RepeatOperations)}.", I think it would be convenient to have some built-in replacement.
IMO this is pertinent because:
It saves a significant effort to anyone that wants to upgrade
I believe it is really something quite intrinsical to an expected Batch API
It implies one of the most sensible ways of dealing with low-level stuff, concurrency and synchronization, and you all are much more aware of how things work in behind
My 2 cents, but thanks either way!
The text was updated successfully, but these errors were encountered:
As per the note "@deprecated with no replacement since 5.0, scheduled for removal in 6.0. Use a custom {@link RepeatOperations} implementation (based on a {@link TaskExecutor} with a bounded task queue) and set it on the step with {@link #stepOperations(RepeatOperations)}.", I think it would be convenient to have some built-in replacement.
IMO this is pertinent because:
My 2 cents, but thanks either way!
The text was updated successfully, but these errors were encountered: