Dialect impala:impala will not make use of SQL compilation caching as it does not set the 'supports_statement_cache' attribute to ``True``.

[ckapolonaris]

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

[proyectopetunia]

seems that cloudera team is not interested in solving the issue.
Probably it is time to change database technology :-(

[contang0]

bump

[doyoungim999]

Is there any update ? The message comes out still. I don't see the error message.

[csringhofer]

@doyoungim999
created PR #582 to set supports_statement_cache=False

I don't know whether it would be safe to set it to True, I don't have a capacity at the moment to dive deeper into sqlalchemy. Any input is welcome if someone knows more about this.
Checked other similar dialects (pyhive, trino-python-client) and they also set it to False, probably for the same reason.