Unable to retrieve Datasets from SST Api #28592
Labels
api
Related to the REST API
Comments
|
To address the issue of fetching datasets from the Superset API and receiving an empty result list despite a successful status code, consider the following potential causes and solutions:
If after checking these areas the issue persists, providing more details about the API call (endpoint, HTTP method, query parameters) and the configuration of the datasets you're attempting to fetch would be helpful for further diagnosis.
|
|
This isue happens even on fresh superset installation, even when there are no previously set access permissions or filters applied. I create the dataset/database using the same users I access the db with. |
|
Considering the issue persists even on a fresh Superset installation without explicit filters or permissions set, it's important to delve deeper into potential causes:
If after these steps the issue remains unresolved, providing detailed information about your API requests (including headers and body) and any specific log entries from Superset related to this issue would be crucial for further diagnosis.
|
|
Everything works fine I get a 200 OK statu code on fetch and even when creating I don't encounter any errors the issue is only on fetching. It's weird that I'm experiencing this issue and yet the admin role has all get api permissions |
|
To tackle the issue of receiving an empty result list when fetching datasets from the Superset API, despite a successful HTTP 200 OK status, let's focus on specific areas for troubleshooting:
By focusing on these specific areas, you should be able to diagnose and resolve the issue of fetching datasets. If the problem persists, providing more details about your API requests and any specific log entries related to this issue would be helpful for further assistance.
|
|
I don't incluse any query params when fetching, I am using superset 4.0.1. Here are my logs |
|
Did you find any error? |
|
The logs you've shared don't show any explicit errors related to fetching datasets, which suggests the issue might not be due to an error in the request itself but could be influenced by other factors. Here are some focused areas to investigate:
Since the issue persists without clear errors and under Admin permissions, it points towards a more subtle configuration or permissions issue rather than a straightforward bug.
|
|
I'm also experiencing this very same issue. I return results when I call the API via the Swagger UI, but not from outside the swagger - authenticating via /login and getting a csrf token, then calling GET /dataset endpoint |
|
Do this remove permissions from the public role and let them be blank that
worked for me
…On Mon, 8 Jul 2024, 19:08 Ian Klek, ***@***.***> wrote:
I'm also experiencing this very same issue
—
Reply to this email directly, view it on GitHub
<#28592 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXMZT7QD66R7BMAI3RUSTS3ZLK2PNAVCNFSM6AAAAABH6FGFFKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJUGU3DCNBTGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
You star!!! That worked 🎉 Thanks very much |
|
Sounds like this issue was effectively solved. Optimistically closing, but holler if this needs to be reopened. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description
I recently created some datasets on superset using superset api using dataset endpoints, The datasets were created successfully but once I fetched them I got an empty result list. I fetch using the same user that created the dataset and the user has an Admin role.
How to reproduce the bug
Screenshots/recordings
No response
Superset version
4.0.1
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: