xujipm commented on issue #28596:
URL: https://github.com/apache/superset/issues/28596#issuecomment-2121624763

   I've tried your steps but still can't solve my problem @dosu.
   
   > It sounds like you're encountering a permissions issue or a problem with 
database connectivity or table existence. Here are some targeted steps to 
troubleshoot and hopefully resolve the issue:
   > 
   > 1. **Verify Role and Permissions**: Ensure the `testRole` you created and 
assigned to the user indeed has the necessary permissions for SQL Lab and the 
`examples.main` schema. Specifically, check for permissions related to database 
and datasource access, such as `DATABASE_SECURITY_ACCESS_ERROR` or 
`DATASOURCE_SECURITY_ACCESS_ERROR`.
   > 2. **Check Database Permissions**: Confirm that the database access is 
explicitly granted to the user's role. This is crucial for non-Admin users and 
involves adding the database to the list of permitted databases for the role.
   > 3. **Review Custom Roles**: If you've created custom roles, make sure they 
include the correct permissions for SQL Lab and database access. It's 
recommended to create new roles with the necessary permissions rather than 
altering base roles.
   > 4. **Database Connectivity**: Ensure there's no issue with the database 
connection itself. Superset uses SQLAlchemy engines for database connections, 
and issues here could lead to the errors you're experiencing.
   > 5. **Table Existence**: Verify that the table `main.part_lines` actually 
exists and that the user has permissions to access it. The error message 
suggests there might be an issue with accessing this specific table.
   > 
   > If these steps don't resolve the issue, providing the exact error message 
from the Superset logs could offer more insight into the problem.
   > 
   > #### Details
   > _To continue the conversation, 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]

Reply via email to