-
Notifications
You must be signed in to change notification settings - Fork 549
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
Adding compatibility with SQLAlchemy 2.0 #457
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mdeshmu
force-pushed
the
sqlalchemy-2.0-support
branch
2 times, most recently
from
June 23, 2023 18:00
d1bf344
to
eb1ed24
Compare
mdeshmu
commented
Jun 25, 2023
mdeshmu
commented
Jun 25, 2023
mdeshmu
commented
Jun 25, 2023
mdeshmu
commented
Jun 25, 2023
mdeshmu
commented
Jun 25, 2023
mdeshmu
commented
Jun 25, 2023
mdeshmu
commented
Jun 25, 2023
mdeshmu
commented
Jun 25, 2023
mdeshmu
changed the title
Adding Compatibility with SQLAlchemy 2.0
Adding compatibility with SQLAlchemy 2.0
Jun 25, 2023
mdeshmu
commented
Jun 25, 2023
mdeshmu
force-pushed
the
sqlalchemy-2.0-support
branch
3 times, most recently
from
June 27, 2023 14:09
23f6cc2
to
49d582e
Compare
mdeshmu
commented
Jun 28, 2023
mdeshmu
commented
Jun 28, 2023
mdeshmu
commented
Jun 28, 2023
mdeshmu
force-pushed
the
sqlalchemy-2.0-support
branch
from
June 28, 2023 06:39
fae253b
to
838727e
Compare
@bkyryliuk This PR is ready for review. |
bkyryliuk
reviewed
Jul 7, 2023
bkyryliuk
reviewed
Jul 7, 2023
bkyryliuk
approved these changes
Jul 7, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LG%small nits
mdeshmu
force-pushed
the
sqlalchemy-2.0-support
branch
from
July 8, 2023 02:09
7d533b7
to
08d062f
Compare
mdeshmu
force-pushed
the
sqlalchemy-2.0-support
branch
from
July 8, 2023 02:16
419bd66
to
112c707
Compare
This was referenced Jul 14, 2023
9 tasks
betodealmeida
added a commit
to preset-io/PyHive
that referenced
this pull request
Aug 8, 2024
* feat: add HTTP and HTTPS to hive (dropbox#385) * feat: add https protocol * support HTTP * fix: make hive https py2 compat (dropbox#389) * fix: make hive https py2 compat * fix lint * Update README.rst (dropbox#423) * chore: rename Trino entry point (dropbox#428) * Support for Presto decimals (dropbox#430) * Support for Presto decimals * lower * Use str type for driver and name in HiveDialect (dropbox#450) PyHive's HiveDialect usage of bytes for the name and driver fields is not the norm is causing issues upstream: apache/superset#22316 Even other dialects within PyHive use strings. SQLAlchemy does not strictly require a string, but all the stock dialects return a string, so I figure it is heavily implied. I think the risk of breaking something upstream with this change is low (but it is there ofc). I figure in most cases we just make someone's `str(dialect.driver)` expression redundant. Examples for some of the other stock sqlalchemy dialects (name and driver fields using str): https://github.com/zzzeek/sqlalchemy/blob/main/lib/sqlalchemy/dialects/sqlite/pysqlite.py#L501 https://github.com/zzzeek/sqlalchemy/blob/main/lib/sqlalchemy/dialects/sqlite/base.py#L1891 https://github.com/zzzeek/sqlalchemy/blob/main/lib/sqlalchemy/dialects/mysql/base.py#L2383 https://github.com/zzzeek/sqlalchemy/blob/main/lib/sqlalchemy/dialects/mysql/mysqldb.py#L113 https://github.com/zzzeek/sqlalchemy/blob/main/lib/sqlalchemy/dialects/mysql/pymysql.py#L59 * Correcting Iterable import for python 3.10 (dropbox#451) * changing drivers to support hive, presto and trino with sqlalchemy>=2.0 (dropbox#448) * Revert "changing drivers to support hive, presto and trino with sqlalchemy>=2.0 (dropbox#448)" (dropbox#452) This reverts commit b0206d3. * Update __init__.py (dropbox#453) dropbox@1c1da8b dropbox@1f99552 * use pure-sasl with python 3.11 (dropbox#454) * minimal changes for sqlalchemy 2.0 support (dropbox#457) * update readme to reflect recent changes (dropbox#459) * Update README.rst (dropbox#475) * Update README.rst (dropbox#476) * feat: JWT support * Add CI to build package --------- Co-authored-by: Daniel Vaz Gaspar <danielvazgaspar@gmail.com> Co-authored-by: Bogdan <b.kyryliuk@gmail.com> Co-authored-by: serenajiang <serena.jiang@airbnb.com> Co-authored-by: Usiel Riedl <usiel.riedl@gmail.com> Co-authored-by: Multazim Deshmukh <57723564+mdeshmu@users.noreply.github.com> Co-authored-by: nicholas-miles <nicholas.miles6@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR includes minimal changes to add SQLAlchemy 2.0 support without breaking compatibility with SQLAlchemy 1.3 and SQLAlchemy 1.4.
Test Environment
SQLALchemy 1.3.24, 1.4.36, and 2.0.16 was used with this hive docker setup for running the test cases. Trino isn't present in that setup, so I added the below lines to docker-compose.yaml and copied trino config from pyhive repository to the Trino container as a volume. That's it, My testing setup was ready.
trino:
image: trinodb/trino:351
ports:
- "18080:18080"
volumes:
- ./trino:/etc/trino
Software versions used in test setup
Hive version - 2.3.2
Presto version - 0.181
Trino version - 351
Local test case run results: