[KUDU-3143] Properties based API for client configuration

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: client
• Labels: roadmap-candidate supportability
• Assignee: Unassigned
• Reporter: Grant Henke
• Created: 02/Jun/20 21:29
• Updated: 03/Jun/20 02:58

Description

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

Issue Links

• is related to: KUDU-2255 Customized configuration on KuduClient via KuduContext
• is related to: KUDU-1948 Client-side configuration of cluster details
• is related to: KUDU-2467 Support client configurations in kudu-spark