None of the create* methods should be too bad. They aren't going to do
much until you use them (e.g. Scanner, BatchScanner, BatchWriter).
getUserAuthorizations is going to be an Accumulo RPC and a (cached)
ZooKeeper lookup in the server. This won't be bad unless you're calling
it in a really tight loop. This would be something fairly easy to cache
(and occasionally refresh).
z11373 wrote:
Hi Keith/Josh,
Are createScanner, createMultiTableBatchWriter, and
connector.securityOperations().getUserAuthorizations expensive operations?
Apparently, I also cache them (called during initialization of my object
that being cached), and now I am not sure if not caching the connector (and
those additional calls) is good idea. One possible option I can think of is
using cache that expires after a period of time. With that, I may be able to
achieve better performance, and avoid this busted connector issue. What do
you guys think?
Thanks,
Z
--
View this message in context:
http://apache-accumulo.1065345.n5.nabble.com/cached-connector-tp16202p16282.html
Sent from the Developers mailing list archive at Nabble.com.
