Bug description
I'm using aurora as the database but when I check back to the table nothings wrong everything is perfect in the database. But when I go to the superset it shows this error, either it c2 or c3 Can anybody help ?
Screenshots/recordings
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
- [ ] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [ ] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [ ] 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.
Comment From: dosubot[bot]
Hey @bradley-jt! I'm here to help you with any bugs, questions, or contributions. Let's tackle this issue together!
The error message you're encountering suggests that the cursor being used in your SQL query is not configured to support backward scanning, which is typically enabled by the SCROLL option. Unfortunately, I couldn't find specific documentation or code comments in Superset that explain how to enable the SCROLL option for cursors [1].
To address this issue, you might need to modify the database connection or query execution settings to enable SCROLL for cursors. This could involve adjusting the database engine specifications or the way queries are executed in Superset. You may want to check the superset/db_engine_specs/aurora.py file, which contains the configuration for Aurora database connections, to see if there are any options related to cursor behavior that can be adjusted [2].
If the issue persists, consider reviewing the database-specific documentation for Aurora to see if there are any settings or configurations that need to be applied to support SCROLL cursors.
To continue talking to Dosu, mention @dosu.
Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other
Comment From: bradley-jt
In the aurora side its good i already test for the cursor backward so I think the problem is in the superset
Comment From: hainenber
Sadly AWS Aurora isn't in the official list of supported databases. We'd be happy to receive a PR to support the database, btw!
Comment From: rusackas
Indeed, we'd love to support more databases. If you want to contribute this, @betodealmeida and/or @villebro might be able to help out.
Comment From: rusackas
Anyone interested in contributing official support for Aurora? For now, I'll move this to an "Ideas" Discussion since it's not a bug, but we'd welcome the contribution from anyone willing.