Bundles with all GET requests can use a single transaction for better performance

[punktilious]

Is your feature request related to a problem? Please describe.
Currently bundles containing only GET requests and of type BATCH use a transaction per request. Better throughput can be achieved if a single transaction is used for the entire request. Because the request is read-only, this does not change the semantics of the request.

Describe the solution you'd like
Use a single transaction if the bundle contains only GET requests.

Describe alternatives you've considered
Recommend that such requests are sent with a bundle type of TRANSACTION, not BATCH.

[punktilious]

To verify, posted batch bundles with different combinations of GET, DELETE and PUT entries. In each case, inspection of the logs showed that the transaction scope was correct.

It was also noted that when a READ fails as part of a read-only batch bundle, the transaction is no longer rolled back but committed. This allows values held in the thread-local caches to be propagated to the shared caches and not be thrown away (which would be a waste).

[punktilious]

It was further confirmed that bundles of type transaction will fail if one of the entries fails. The transaction is marked for rollback in this case, although it would be more optimal to commit in the case of a purely read-only scenario. A new issue will be raised for this.