Added Kerberos for Trino to connect to Phoenix

[zxl333]

Description

This pr is new feature for phoenix connector.When the hbase cluster is Kerberos, the original trino does not support connections .The Phoenix connection string is changed to the following. phoenix.connection-url=jdbc:phoenix:host1,host2,host3:2181:/hbase:kerberos principal:kerberos keytab path example: phoenix.connection-url=jdbc:phoenix:host-192-168-253-13,host-192-168-253-14,host-192-168-253-15:2181:/hbase:hbase/[email protected]:/etc/security/keytabs/hbase.keytab

Related issues, pull requests, and links

Documentation

( ) No documentation is needed. ( ) Sufficient documentation is included in this PR. ( ) Documentation PR is available with #prnumber. ( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

( ) No release notes entries required. ( ) Release notes entries required with the following suggested text:

# Section
* Fix some things. ({issue}`issuenumber`)

[cla-bot[bot]]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: 曾新亮. This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email [email protected]
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[zxl333]

https://github.com/trinodb/trino/issues/3426

[Praveen2112]

Thanks for working on this. Can we have a PTs for Phoenix in a Kerberized environment

[cla-bot[bot]]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: 曾新亮. This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email [email protected]
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-bot[bot]]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: 曾新亮. This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email [email protected]
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-bot[bot]]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: 曾新亮. This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email [email protected]
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[zxl333]

Thanks for working on this. Can we have a PTs for Phoenix in a Kerberized environment

What does PTs mean @Praveen2112

[hashhar]

PT = Product test. You basically provide a dockerized setup with kerberos + Phoenix similar to EnvMultinodePhoenix5 but with a kerberized Phoenix instead and then run some tests against it like https://github.com/trinodb/trino/blob/master/testing/trino-product-tests/src/main/java/io/trino/tests/product/phoenix/TestPhoenix.java

[mosabua]

:wave: @zxl333 @hashhar - this PR has become inactive. We hope you are still interested in working on it. Please let us know, and we can try to get reviewers to help with that.

We're working on closing out old and inactive PRs, so if you're too busy or this has too many merge conflicts to be worth picking back up, we'll be making another pass to close it out in a few weeks.