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
In our code, we have several workers running simple queries such as below. However, we started seeing errors where pandas had a difficulty wrapping the result into a dataframe with specific dtype for columns, throwing this error KeyError: "Only a column name can be used for the key in a dtype mappings argument. 'ts' not found in columns."
We believe that this might have been caused by high load on the Vertica service, where the resource pool might have been exceeded. It could also have been a red herring, hence, why I am reaching out for some insights. When we reran the process only for the uuids for which we had this issue, code execution passed without errors.
Are there messages returned by Vertica which are not considered errors in vertica-python?
Or are not all vertica errors thrown by vertica-python?
Or is there something else that could have happened in this scenario, not covered by vertica-python?
In theory vertica-python handles server errors correctly, there must be an exception thrown. For a server notice, vertica-python issues a warning message.
Since you are using sqlalchemy-vertica-python, the problem might be inside it. You should check what sql sqlalchemy-vertica-python passes to vertica-python, and what query results returned by vertica-python.
Note that vertica/vertica-sqlalchemy-dialect is the official Vertica SQLAlchemy dialect, sqlalchemy-vertica-python is not official. We can help you better if you provide a reproducer using pure vertica-python or using vertica/vertica-sqlalchemy-dialect.
In our code, we have several workers running simple queries such as below. However, we started seeing errors where pandas had a difficulty wrapping the result into a dataframe with specific dtype for columns, throwing this error
KeyError: "Only a column name can be used for the key in a dtype mappings argument. 'ts' not found in columns."
We believe that this might have been caused by high load on the Vertica service, where the resource pool might have been exceeded. It could also have been a red herring, hence, why I am reaching out for some insights. When we reran the process only for the uuids for which we had this issue, code execution passed without errors.
Are there messages returned by Vertica which are not considered errors in vertica-python?
Or are not all vertica errors thrown by vertica-python?
Or is there something else that could have happened in this scenario, not covered by vertica-python?
Code:
The text was updated successfully, but these errors were encountered: