Added server side parameters for thrift connection type

[hanna-liashchuk]

resolves #387

Description

PR allows passing spark/hive configurations for thrift connections via server_side_parameters in the profiles file.

Checklist

• I have read the contributing guide and understand what's expected of me
• I have signed the CLA
• 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
• I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR - Added server_side_parameters for thrift connection method docs.getdbt.com#2629
• I have run changie new to create a changelog entry

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Hanna Liashchuk.
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@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Hanna Liashchuk.
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@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[hanna-liashchuk]

Hi @rhousewright @drewbanin, could you please review this PR?

[cla-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@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-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@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-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@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-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@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-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@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[VShkaberda]

Description has been added already to the Apache Spark Profile in Dbt docs.

[Fleid]

Hi @hanna-liashchuk, thanks so much for your contribution.
I see we have a duplicate issue and PR for that exact scenario (#590 and #591).

Your approach is to re-purpose server_side_parameters from the ODBC method. Their approach is to create a new configuration string spark_conf_string that then needs to be parsed.

I have a preference for your approach as it makes the profiles.yml schema consistent across methods.
Any thoughts about that?

[hanna-liashchuk]

@Fleid Agree, I think keeping the same name for the parameter is more user and documentation friendly.

[Fleid]

Hey @hanna-liashchuk, sorry for the delay, but we're still weighing options.
There is a conversation going on in the other PR if you want to chime in ;)
That's #591

[JCZuurmond]

@Fleid : This one is ready to merge. I expect a rebase is needed on main to fix the CI. Could you or @colin-rogers-dbt fix this?

[tanvn]

@Fleid @JCZuurmond
Hi, we are using Thrift connections for our project and looking forward to giving this feature a try.
May I know if there is any update on this?
If there is anything I can do, please feel free to let me know.