You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by GitBox <gi...@apache.org> on 2019/01/31 18:24:12 UTC

[GitHub] milleruntime commented on issue #914: Revert TableOps.exists() behavior. Closes #768

milleruntime commented on issue #914: Revert TableOps.exists() behavior. Closes #768
URL: https://github.com/apache/accumulo/pull/914#issuecomment-459451516
 
 
   I did a little more git log research...
   5adeb4b7ed561a0bcea1a1def17835310831662f
   ACCUMULO-4778 Cache table name to id map (#364)
   This commit was done in the 1.9.0 and forward.  So the behavior of the exists method in 1.8.1 (and prior) was to check the ZooCache every time. 
   
   The more I think about it, I think we should revert the behavior of this method back to just using the ZooCache, like we did in 1.8.1.  I feel this is a good compromise.  Other areas of Accumulo will gain the benefits of the cache but the behavior of this method will go back to what was expected in previous releases.  
   
   Anyone else have thoughts on this?

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services