-
Notifications
You must be signed in to change notification settings - Fork 13.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SQL Lab Error 'str' object has no attribute 'set' #29611
Comments
Hey @deviardn! 👋 I'm here to help you with any bugs, questions, or contributions you have while waiting for a human maintainer. Let's squash those bugs together! To resolve the "Microsoft SQL Server Error: 'str' object has no attribute 'set'" error in Apache Superset version 4.0.2 when using the SQL Lab menu, you should apply the fix from the pull request #27577 which addresses issues with SQL Server in the Here is the relevant fix: # Ensure you have the latest version of sqlglot that includes the fix for SQL Server.
# You can update sqlglot by running:
pip install --upgrade sqlglot This update should resolve the error by ensuring that the correct handling for SQL Server is applied [1]. |
Not sure if it's related or the same issue to the issue I'm facing: |
If these are the same, let's close one in favor of the other. |
@rusackas I've tested the suggestion with sqlglot, it's not the same issue. |
I have captured the error log here:
|
Bug description
Sorry, my English is not good. I am using apache superset version 4.0.2. I tried using the SQL Lab menu, I got an error like in the picture. what do I have to do? Thank You
![apache_superset_4_2](https://private-user-images.githubusercontent.com/6567330/349338279-8fe15b65-64d5-4ac3-a884-d2dd69754855.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU4MjI5NzUsIm5iZiI6MTcyNTgyMjY3NSwicGF0aCI6Ii82NTY3MzMwLzM0OTMzODI3OS04ZmUxNWI2NS02NGQ1LTRhYzMtYTg4NC1kMmRkNjk3NTQ4NTUucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDkwOCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA5MDhUMTkxMTE1WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZDA3ZDQxOTZlMTBmNTVjNzhhNGZhNWUwZTk3YWFiMGVlZjAxZWYzNWFhMjg1ZjU5NTA1NWI5NDliNWViZmFhNiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.MtSiEg5DmBjgCrxBk9WfKF3umuVEHEQScxgppjaBwrI)
How to reproduce the bug
Screenshots/recordings
No response
Superset version
4.0.2
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: