dosubot[bot] commented on issue #30208:
URL: https://github.com/apache/superset/issues/30208#issuecomment-2340128791

   <!-- Greeting -->
   Hello, @aswathinj-pai! I'm here to help you with any bugs, questions, or 
contributions. Let's tackle this issue together!
   
   <!-- Answer -->
   I found a similar issue related to database connections and schema fetching 
in Apache Superset. In one case, users were unable to view tables under a 
specific schema due to the need to set the **schema** parameter in the **Edit 
Tables** form (Sources > Tables > Edit record) 
<sup>[[1]](https://github.com/apache/superset/blob/master/docs/docs/configuration/databases.mdx)</sup>.
   
   To address your issue, try the following steps:
   
   1. **Set the Schema Parameter**:
      - Go to **Sources > Tables** in the Superset UI.
      - Edit the table record and set the **schema** parameter to the specific 
schema you are trying to access.
   
   2. **Verify the Connection String**:
      - Ensure that your SQLAlchemy URI is correctly formatted for the Spark 
Thrift Server. It should look something like this:
        ```
        hive://hive@{hostname}:{port}/{database}
        ```
      - Replace `{hostname}`, `{port}`, and `{database}` with your actual Spark 
Thrift Server details 
<sup>[[1]](https://github.com/apache/superset/blob/master/docs/docs/configuration/databases.mdx)</sup>.
   
   3. **Check for Driver Issues**:
      - Make sure you have the `pyhive` package installed, as it is required 
for connecting to Spark SQL via the Hive Thrift Server:
        ```bash
        pip install pyhive
        ```
   
   If these steps do not resolve the issue, it might be related to a known 
limitation or bug in Apache Superset 4.0.1. For example, there are limitations 
with schema fetching and database connections for certain databases 
<sup>[[2]](https://github.com/apache/superset/blob/master/superset/db_engine_specs/README.md)</sup>.
   
   If the problem persists, you might want to check the Superset logs for more 
detailed error messages that could provide further insights.
   
   
   <!-- 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]

Reply via email to