fix: update to use pyhive function to get compatible sasl

[ntnhaatj]

resolves dbt-labs/dbt-adapters#475
docs dbt-labs/docs.getdbt.com/#

Problem

Current SASL factory for TSaslClientTransport using SASLClient from pure-sasl which is incompatible with pyhive

Solution

Pyhive provides a wrapper PureSASLClient which implement some missing methods to interact with thrift-sasl.

This MR update to use get_installed_sasl of pyhive to decide which sasl client should be use in current environment.

Checklist

• I have read the contributing guide and understand what's expected of me
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: nhat.nguyent.
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]

Thanks for your pull request, and welcome to our community! We require contributors to sign our Contributor License Agreement and we don't seem to have your signature on file. Check out this article for more information on why we have a CLA.

In order for us to review and merge your code, please submit the Individual Contributor License Agreement form attached above above. If you have questions about the CLA, or if you believe you've received this message in error, please reach out through a comment on this PR.

CLA has not been signed by users: @ntnhaatj

[cla-bot]

Thanks for your pull request, and welcome to our community! We require contributors to sign our Contributor License Agreement and we don't seem to have your signature on file. Check out this article for more information on why we have a CLA.

In order for us to review and merge your code, please submit the Individual Contributor License Agreement form attached above above. If you have questions about the CLA, or if you believe you've received this message in error, please reach out through a comment on this PR.

CLA has not been signed by users: @ntnhaatj

[nqvuong1998]

Hi @McKnight-42 @mikealfare , any update for this PR?

[github-actions]

This PR has been marked as Stale because it has been open with no activity as of late. If you would like the PR to remain open, please comment on the PR or else it will be closed in 7 days.

[alek6dj]

Hello. Will this PR be included in the official code? In our case, it solved a connectivity issue for a major banking client in a Cloudera ecosystem, with Kerberos authentication and a Livy Thrift server.