Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ADAP-799] [Feature] Investigate removing dependency on PyHive #868

Open
3 tasks done
colin-rogers-dbt opened this issue Aug 14, 2023 · 2 comments
Open
3 tasks done
Labels
enhancement New feature or request Stale triage

Comments

@colin-rogers-dbt
Copy link
Contributor

Is this your first time submitting a feature request?

  • I have read the expectations for open source contributors
  • I have searched the existing issues, and I could not find an existing issue for this feature
  • I am requesting a straightforward extension of existing dbt-spark functionality, rather than a Big Idea better suited to a discussion

Describe the feature

PyHive is in KTLO mode and is not well supported. We should investigate if we still need this dependency or if we can replace it with something else. If we truly need this dependency we may need to look into forking and maintaining ourselves.

Currently PyHive is blocking support for py3.11 simply because we need them to publish a release.

Describe alternatives you've considered

No response

Who will this benefit?

No response

Are you interested in contributing this feature?

No response

Anything else?

No response

@github-actions github-actions bot changed the title [Feature] Investigate removing dependency on PyHive [ADAP-798] [Feature] Investigate removing dependency on PyHive Aug 14, 2023
@github-actions github-actions bot changed the title [ADAP-798] [Feature] Investigate removing dependency on PyHive [ADAP-799] [Feature] Investigate removing dependency on PyHive Aug 14, 2023
@colin-rogers-dbt
Copy link
Contributor Author

@JCZuurmond - This is a more future oriented idea than #864

@mikealfare mikealfare removed the jira label Feb 7, 2024
Copy link
Contributor

github-actions bot commented Aug 6, 2024

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

@github-actions github-actions bot added the Stale label Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Stale triage
Projects
None yet
Development

No branches or pull requests

2 participants