...
The other thing to note is this approach does not provide read your own writes. Reads within the transaction cannot request newest copy which contains its own write, since the transaction is not committed thus the cached copy may not be correct. It will be correct until HMS apply all writes of the transaction from notification log. So the reads might end up reading the old copy from cache (consider the next read route to the other HMS). I am not sure if there’s a use case read the entry just written in Hive. If it does, we need to cache the written copy in client, so the next time client reads, it will be retrieved from client cache to make sure it contains its own writes.
...