DB ERROR

[Michuk02]

Bug description

I try to import a filter based on the source of information, of which there are two, i can;t choose either of them because i get an error, provided on a screen below. I work on Apache Superset from Google Cloud of my company.

How to reproduce the bug

Created a dataset and cant pick any value from the fillter because i get 1011 error.

Screenshots/recordings

Superset version

master / latest-dev

Python version

I don't know

Node version

I don't know

Browser

Not applicable

Additional context

No response

Checklist

• [X] I have searched Superset docs and Slack and didn't find a solution to my problem.
• [X] I have searched the GitHub issue tracker and didn't find a similar bug report.
• [X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[dosubot[bot]]

@Michuk02 Hello there! I'm here to help you with any bugs, questions, or even becoming a contributor. Let's squash those bugs together! 🤖

To resolve the "DB engine Error" with error code 1011 when trying to import a filter in Apache Superset on Google Cloud, follow these steps:

1. Check Superset Logs: Look at the Superset logs to get more details about the error. This can provide more context on what went wrong.
2. Database Connection: Ensure that the database connection parameters are correct and that the database is accessible.
3. Superset Configuration: Verify that your Superset configuration is correct and that all necessary parameters are set.
4. Update Superset: Make sure you are using the latest version of Superset, as the issue might have been fixed in a newer release.
5. Google Cloud Environment: Check if there are any specific issues or limitations in your Google Cloud environment that might be causing the error.

Additionally, for BigQuery-specific issues:

6. Verify BigQuery Permissions: Ensure that the service account used has the necessary permissions, such as "BigQuery Data Viewer", "BigQuery Metadata Viewer", "BigQuery Job User", and permissions like "bigquery.readsessions.create" and "bigquery.readsessions.getData".
7. Check for Specific Errors: Look for specific error patterns in the logs, such as:
   • Access Denied: Ensure the service account has the required permissions.
   • Table Does Not Exist: Verify that the table name and dataset are correct.
   • Column Does Not Exist: Check if the column names in your query are correct.
   • Schema Does Not Exist: Ensure the schema specified in the query exists.
   • Syntax Errors: Review your SQL query for any syntax errors.

For the "Unexpected param" error:

• Ensure all template parameters in your query are surrounded by double braces, e.g., {{ ds }}.
• Verify that the parameters are correctly formatted and not missing any required values.
• Double-check the syntax and structure of your query to avoid any typos or errors.

If the issue persists, provide more specific details from the logs or error messages to further diagnose the problem ^[1][2][3].

To continue talking to Dosu, mention @dosu.