troubleshooting
How to fix the error 'Failed to get/set session config: Unrecognized config entry `transaction isolation level`' when connecting Superset with Risingwave?
I am following the guide to connect Superset with Risingwave, but keep getting the error 'Failed to get/set session config: Unrecognized config entry transaction isolation level
'. Yuhao Su mentioned that the bug was due to a difference in the format of the transaction isolation level command between PostgreSQL and Risingwave. The fix will be released in Risingwave v1.5.1. How can I fix this error in the current version?
Jo
Jochen Christ
Asked on Dec 14, 2023
- The error is caused by a difference in the format of the transaction isolation level command between PostgreSQL and Risingwave.
- Risingwave only supports the format
show transaction_isolation_level;
, while PostgreSQL allows bothshow transaction isolation level;
andshow transaction_isolation_level;
. - To fix this error in the current version, you can manually adjust the transaction isolation level command in the Superset configuration to match Risingwave's format.
Example:
# Update the transaction isolation level command in the Superset configuration
config['SQLALCHEMY_EXTRAS'] = {
'engine_params': {
'isolation_level': 'READ COMMITTED'
}
}
- Alternatively, you can wait for the fix to be released in Risingwave v1.5.1 next week.
Dec 15, 2023Edited by