Using apache kudu docker images and update kudu-client version

[laglangyue]

motivation

we use the kudu images but not from apache，so update it, and update the version Although I am not an expert in kudu, I am capable of solving this problem. I did some digging and found that the new version of kudu will try TLS connection, so the connection failed

test

test it locally ok

future

I add encryptionPolicy(EncryptionPolicy.OPTIONAL) to client temporaryly. It need to some improvment for client. In my opinion, we should provide a way for users to pass us a client that can be customized by the user

  public enum EncryptionPolicy {
    // Optional, it uses encrypted connection if the server supports it
    // but it can connect to insecure servers too.
    OPTIONAL,
    // Only connects to remote servers that support encryption, fails
    // otherwise. It can connect to insecure servers only locally.
    REQUIRED_REMOTE,
    // Only connects to any server, including on the loopback interface,
    // that support encryption, fails otherwise.
    REQUIRED,
  }

[laglangyue]

@pjfanning I know you've made some efforts for Kudu before, what do you think?

[laglangyue]

reference to https://github.com/apache/kudu/blob/master/docker/quickstart.yml

[laglangyue]

I check the log about container.

Then I found a issue about kudu TLS https://issues.apache.org/jira/browse/KUDU-2647

[laglangyue]

I check it again, I add a config for EncryptionPolicy. PTAL @pjfanning In fact, implementation of kudu connector is too simple, and If I have time, I will submit a pr in futrue.

[pjfanning]

Thanks - I've restarted the CI runs

[pjfanning]

Thanks @laglangyue - merged. I have labelled this as needing a mention in the release notes due to the new config.