keith-turner commented on PR #3187: URL: https://github.com/apache/accumulo/pull/3187#issuecomment-1420122157
> My understanding is that the specific use case is consistency from the same client, to ensure that a previous write is visible on subsequent scans. I don't believe this was for same client. The wait for write behavior is for the following case. 1. client does a write and then the client process dies 2. client process starts again and does a read, expecting to see anything it wrote before. However if the write is still in flight on the tserver side it may not see it. Within the same process if a client always flushes the batch writer before reading it will see the changes w/o this check. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
