In record layer, long running queries are supported by concept of continuation.
After firing a query, client gets some query results and a continuation as output. It can then use this continuation to again open a (new) transaction and get remaining results. This can be done repeatedly.
Is my understanding correct?
Beacuse we are doing one big query in multiple fdb transactions (or on multiple db snapshots), we might get inconsistent result (as a whole).
Is this understanding correct?
Or is there some milestoning logic in record layer, which might be storing record with some milestone and fetching record asOf milestone and hence providing consistency on such qureies?
The docs say that RedWood Storage Engine will support long running read transactions. Does this mean that it will make continuation redundant?