[jira] [Updated] (KUDU-3143) Properties based API for client configuration

["Grant Henke (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KUDU-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Grant Henke updated KUDU-3143:
------------------------------
    Labels: roadmap-candidate supportability  (was: roadmap-candidate)

> Properties based API for client configuration
> ---------------------------------------------
>
>                 Key: KUDU-3143
>                 URL: https://issues.apache.org/jira/browse/KUDU-3143
>             Project: Kudu
>          Issue Type: New Feature
>          Components: client
>            Reporter: Grant Henke
>            Priority: Major
>              Labels: roadmap-candidate, supportability
>
> Currently a client/session/scanner/etc needs to be configured via a series of setter methods. This can be cumbersome when plumbing configuration through to the the underlying client in an integration such as Spark/NiFi/Hive because a code change needs to be made every time a new configuration is added to Kudu to expose the configuration in the integration. 
> Instead we could expose an API to pass a Properties object with key/value pairs that are treated as Public API and will set the various configurations accordingly. Using that API a passthrough can be exposed from integration. 
> For an example, this could be used in Spark to expose all relevant configurations instead of the limited list of custom values seen here:
> https://github.com/apache/kudu/blob/master/java/kudu-spark/src/main/scala/org/apache/kudu/spark/kudu/DefaultSource.scala#L58-L72



--
This message was sent by Atlassian Jira
(v8.3.4#803005)