eolivelli commented on issue #853: BP-14 WriteFlag DEFERRED_SYNC Client Side Implementation URL: https://github.com/apache/bookkeeper/pull/853#issuecomment-389165802 @sijie @jvrao My point about LAC: 1) having LAC that is not advancing without guarantees is good to preserve BK feature that "if is it read once it will be always readable" (if you respect LAC). This is current implementation. It will require force() for the LAC to advance. 2) having LAC which advances is like having a per-ledger syncData = false. Option 2) also makes things simpler, and we can implement 1) with an additional WriteFlag. We are talking only about client-side behaviour. So I am leaning towards option 2, I think in BP14 documents we were talking about 1, if @jvrao is OK I will change the implementation. The force() API will enable the client to sync the ledger and get guarantees about persistence
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
