dosubot[bot] commented on issue #29909:
URL: https://github.com/apache/superset/issues/29909#issuecomment-2311229599
<!-- Answer -->
Yes, the fix I proposed applies to your situation, even when using Helm
Chart in a Ruby on Rails environment. The migration scripts
`migrate_native_filters_to_new_schema.py` and
`cleanup_erroneous_parent_filter_ids.py` are designed to update the filter
configurations in the Superset database, which is independent of the deployment
method.
To address the specific error "Cannot load filter. Error: canceling
statement due to conflict with recovery DETAIL: User query might have needed to
see row versions that must be removed," it seems to be related to PostgreSQL's
recovery process. This error typically occurs when a query conflicts with the
database's recovery process, such as during a backup or replication.
Here are the steps you should follow:
1. **Run the Migration Scripts**: Ensure that the migration scripts
`migrate_native_filters_to_new_schema.py` and
`cleanup_erroneous_parent_filter_ids.py` have been executed successfully. These
scripts will update the filter configurations to the new schema and clean up
any erroneous parent filter IDs.
2. **Check PostgreSQL Configuration**: Verify that your PostgreSQL database
is not in recovery mode or undergoing any maintenance that could cause
conflicts with user queries. You may need to consult your database
administrator for this.
3. **Review Helm Chart Configuration**: Ensure that your Helm Chart
configuration for Superset is correctly set up, especially the database
connections. Here is a snippet from the `values.yaml` file for reference:
```yaml
connections:
redis_host: '{{ .Release.Name }}-redis-headless'
redis_port: "6379"
db_host: '{{ .Release.Name }}-postgresql'
db_port: "5432"
db_user: superset
db_pass: superset
db_name: superset
```
4. **Update Superset Configuration**: Make sure that the Superset
configuration is correctly set up to use the new filter schema. This includes
updating the `json_metadata` of your dashboards as per the new schema.
5. **Monitor Logs**: Keep an eye on the Superset logs and PostgreSQL logs
for any additional errors or warnings that could provide more insight into the
issue.
By following these steps, you should be able to resolve the filter
functionality issues and address the PostgreSQL conflict error. If the problem
persists, you may need to further investigate the specific queries causing the
conflict and optimize them accordingly.
<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
