In theory something like this should work, resuming the transaction
after each asynchronous operation:
https://paste.fedoraproject.org/461451/77496416/raw/
I'm not sure about the usability, or performance... The
TransactionManager API doesn't allow asynchronous commit(), so one
might as well
To put some context, that's a very unfavorable query for Lucene (sort by
data other than score, retrieve all the data set).
On Mon 16-10-24 17:42, Sanne Grinovero wrote:
>Hi all,
>at our last meeting we had some chats about heap usage at runtime.
>
>I wasn't actually investigating this, but since
