Skip to content
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

Rockset Error: list index out of range #24988

Closed
3 tasks done
maxreis86 opened this issue Aug 15, 2023 · 1 comment
Closed
3 tasks done

Rockset Error: list index out of range #24988

maxreis86 opened this issue Aug 15, 2023 · 1 comment

Comments

@maxreis86
Copy link

When no results are returned for any query using the Rockset as the backend for a database connection, we receive the error "Rockset Error list index out of range"
In the other hand, when using postgresql as the backend for a database connection we receive the message "No results were returned for this query"
What we expect would be receiving the same message "No results were returned for this query" for Rockset as well.

How to reproduce the bug

  1. Create a new database connection using Rockset as the backend and with a SQLALCHEMY URI
  2. Go to SQL and SQL Lab
  3. Run any query with a filter that returns no results
  4. See error Rockset Error list index out of range

Expected results

Receiving the same message "No results were returned for this query" instead of get an error.

Actual results

We are receiving the error "Rockset Error list index out of range"

Screenshots

image
image

Environment

(please complete the following information):

  • browser type and version: Any
  • superset version: 2.1.1rc2
  • python version: 3.11
  • node.js version: 18.0.0
  • any feature flags active: None

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • I have reproduced the issue with at least the latest released version of superset.
  • I have checked the issue tracker for the same issue and I haven't found one similar.
@rusackas rusackas added data:connect:rockset data:connect Namespace | Anything related to db connections / integrations and removed data:connect Namespace | Anything related to db connections / integrations labels Mar 8, 2024
@rusackas
Copy link
Member

rusackas commented Mar 8, 2024

Hopefully this was resolved if you follow the docs updated by #24649

I'm not sure if this is still an issue in current versions of Superset (3.x). If it is, we can re-open this, or feel free to open a new issue with updated context and a reproducible case. We're no longer supporting Superset 2.x or prior, and it's been a while since this thread saw any activity, so I'm closing this as stale.

@rusackas rusackas closed this as completed Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants