You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Sandish Kumar HN (Jira)" <ji...@apache.org> on 2019/08/29 23:46:00 UTC
[jira] [Commented] (KUDU-2910) Add client cache/factory
implementation to the kudu-client
[ https://issues.apache.org/jira/browse/KUDU-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16919047#comment-16919047 ]
Sandish Kumar HN commented on KUDU-2910:
----------------------------------------
[~granthenke] are we looking for any new features other than what is available in `KuduContext.KuduClientCache`?
> Add client cache/factory implementation to the kudu-client
> ----------------------------------------------------------
>
> Key: KUDU-2910
> URL: https://issues.apache.org/jira/browse/KUDU-2910
> Project: Kudu
> Issue Type: Improvement
> Components: client
> Reporter: Grant Henke
> Assignee: Sandish Kumar HN
> Priority: Major
>
> Often integrations should cache and use a shared client for all communication to a given list of masters. This is seen in our own kudu-spark integration in `KuduContext.KuduClientCache`.
> It would be nice to add a generic implementation to the kudu-client so that this code doesn't get re-written over and over. Additionally we can add more complex logic if useful later.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)