batch | Iterate over Enumerables with progress reporting

It completely depends on what your listener is doing with the data.

If it processes each record in a loop then there is no benefit; you might as well just let the container iterate over the collection and send the listener one record at-a-time.

Batch mode will improve performance if you are processing the batch as a whole - e.g. a batch insert using JDBC in a single transaction.

This will often run much faster than storing one record at-a-time (using a new transaction for each record) because it requires fewer round trips to the DB server.

To get the content as shown in your example TEXT.txt, you could just use a For /F loop and use the = character as the delimiters:

change the posts migration post_id and author_id to this :

be aware I don't have a Windows machine against which to try this, so it's just "best effort"

As best I can tell, your problem is because you are trying to recreate the behavior of win_shell by "manually" invoking that improperly quoted cmd.exe /c business, ending up with cmd.exe /c "cmd.exe /c whatever"; dialing up the ansible verbosity -vv could confirm or deny that pattern

Also, the win_shell docs say to use win_command: unless you have a shell redirect need, which as written your task does not.

The RetryingBatchErrorHandler was added in spring-kafka version 2.5 (which comes with Boot 2.3).

The listener must throw an exception to indicate which record in the batch failed (either the complete record, or the index in the list).

Offsets for the records before the failed one are committed and the failed record can be retried and/or sent to the dead letter topic.

See https://docs.spring.io/spring-kafka/docs/current/reference/html/#recovering-batch-eh

There is a small example there.

The RetryingBatchErrorHandler was added in 2.3.7, but it sends the entire batch to the dead letter topic, which is typically not what you want (hence we added the RetryingBatchErrorHandler).

We're looking in to the same issue currently and it seems apple are disabling the old binary interface which push sharp uses.

https://developer.apple.com/news/?id=c88acm2b

pushsharp has it on the roadmap to support the new interface but not completed yet.

Found this library which seems easy enough to use as a solution. hope this helps.

https://github.com/alexalok/dotAPNS

This is because your ItemProcessorSurveillance implements two interfaces: ItemProcessor and StepExecutionListener but is only registered as an ItemProcessor in the step. It should also be registered as a listener so that beforeStep is called when appropriate to set the stepExecution field.

Inside your requirements.txt change scipy line with this scipy==1.6.0 and save. Now retry pip installation.