Hi Toby, 1) I am not an expert for RocksDB, but I don't see a problem with larger objects.
2) I assume, by "guaranteed" you mean that the commit is performed when the call return. In this case, no. It only sets a flag to commit at the next earliest point in time possible. Ie, you can trigger commits in between the regular commit interval that is configured via "commit.interval.ms" 3) Yes. 4) Yes. -Matthias On 05/26/2016 02:36 PM, Tobias Adamson wrote: > Hi > We have a scenario where we could benefit from the new API’s instead of our > in house ones. > However we have a couple of questions > > 1. Is it feasible to save 2-3MB size values in the RocksDBStorage? > 2. When is the offset committed as processed when using a custom Processor, > is it when you call commit on the context and is the commit guaranteed? > 3. Is it ok to put values in to the KVStore in the punctuate method? > 4. Is the punctuate method run by the same thread as the process method? > > > Regards > Toby >
signature.asc
Description: OpenPGP digital signature
