Record Layer Design Questions

[rajivr (Rajiv M Ranganath)]

As mentioned in the following post

Key-val sizes in the Record Layer

Hm, the feature alluded to in the paper there is just that singe records are split across multiple key-value pairs, so single records are not subject to the 100 kB “max value” size limit. The “catch” is: The Record Layer will choose to split your record so that each value (except the last) is 100 kB in size (right up to the limit). It’s possible that the key value store would do better if the data were split across more, smaller keys; it’s also possible that 100 kB is optimal, but we haven’t …

It looks to me that RecordLayer does not track the 10MB limit for transactions and makes the higher level code responsible for handling “transaction_too_large (2101)” error. Just want to confirm that it is still the case?

While exceeding the 10MB limit would result in a transaction too large error, in our application, we could inadvertently exceed the 1MB limit, thereby causing a performance issue.

I was wondering if some mechanism exists within Record Layer and FoundationDB that would let us log such transactions, so we can investigate them later on?

The only mechanism that I was able to think of was to set the transaction option SizeLimit to 1MB, but that would fail any transaction larger than 1MB. Is there some option that would allow us to log transactions larger than 1MB, but not fail them?