You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There may already be a way to accomplish this, but I was hoping there may be a way to maintain connection to a remote Thrift server in-between requests. We're developing a RESTful API to provide basic reads of our HBase cluster, but are experiencing slow response times because (we think) a new connection is established for each read. Are you able to recommend a solution to this?
I envision this solution looking similar to the massive_record gem or active_record approach.
The text was updated successfully, but these errors were encountered:
Yeah, you definitely don't want to instantiate a new thrift connection on every request. You should create the connection and memoize/cache it somehow; in an initializer or as a class variable, etc.
Did you see this comment from a previous issue? #15 (comment)
Yeah, you definitely don't want to instantiate a new thrift connection on
every request. You should create the connection and memoize/cache it
somehow; in an initializer or as a class variable, etc.
Did you see this comment from a previous issue? #15 (comment)#15 (comment)
Reply to this email directly or view it on GitHubhttps://github.com//issues/17#issuecomment-38642483
.
There may already be a way to accomplish this, but I was hoping there may be a way to maintain connection to a remote Thrift server in-between requests. We're developing a RESTful API to provide basic reads of our HBase cluster, but are experiencing slow response times because (we think) a new connection is established for each read. Are you able to recommend a solution to this?
I envision this solution looking similar to the massive_record gem or active_record approach.
The text was updated successfully, but these errors were encountered: