You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello to everyone! When I'm attempting to write a dataframe to an impala database, with the Pandas function "to_sql" and a SQLAlchemy engine I get the message:
"/usr/local/lib/python3.8/dist-packages/pandas/io/sql.py:857: SAWarning: Dialect impala:impala will not make use of SQL compilation caching as it does not set the 'supports_statement_cache' attribute to True. This can have significant performance implications including some performance degradations in comparison to prior SQLAlchemy versions. Dialect maintainers should seek to set this attribute to True after appropriate development and testing for SQLAlchemy 1.4 caching support. Alternatively, this attribute may be set to False which will disable this warning. (Background on this error at: https://sqlalche.me/e/14/cprf)
result = conn.execute(self.table.insert(), data)"
Impyla Version: 0.18.0
The text was updated successfully, but these errors were encountered:
Hello to everyone! When I'm attempting to write a dataframe to an impala database, with the Pandas function "to_sql" and a SQLAlchemy engine I get the message:
"/usr/local/lib/python3.8/dist-packages/pandas/io/sql.py:857: SAWarning: Dialect impala:impala will not make use of SQL compilation caching as it does not set the 'supports_statement_cache' attribute to
True
. This can have significant performance implications including some performance degradations in comparison to prior SQLAlchemy versions. Dialect maintainers should seek to set this attribute to True after appropriate development and testing for SQLAlchemy 1.4 caching support. Alternatively, this attribute may be set to False which will disable this warning. (Background on this error at: https://sqlalche.me/e/14/cprf)result = conn.execute(self.table.insert(), data)"
Impyla Version: 0.18.0
The text was updated successfully, but these errors were encountered: