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

Example datasets created with incorrect schema #16051

Closed
3 tasks done
betodealmeida opened this issue Aug 3, 2021 · 3 comments
Closed
3 tasks done

Example datasets created with incorrect schema #16051

betodealmeida opened this issue Aug 3, 2021 · 3 comments
Assignees
Labels
#bug Bug report

Comments

@betodealmeida
Copy link
Member

When running load-examples, the example datasets defined in superset/examples/configs/ are loaded without a schema.

Expected results

Datasets should have the correct schema.

Actual results

Datasets end without a schema, even if one is being used.

Screenshots

N/A

How to reproduce the bug

  1. Run superset load-examples
  2. Check the schema of all datasets, the ones loaded from configs have it set to null.

Environment

  • superset version: superset version
  • python version: python --version
  • node.js version: node -v
  • any feature flags active:

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.

Additional context

N/A

@stale
Copy link

stale bot commented Apr 30, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

@stale stale bot added the inactive Inactive for >= 30 days label Apr 30, 2022
@rusackas
Copy link
Member

@betodealmeida do you know if this issue still exists, or if it was resolved by #16041 ?

@stale stale bot removed the inactive Inactive for >= 30 days label Jan 13, 2023
@rusackas
Copy link
Member

Closing this as stale since it's been silent for so long, and we're trying to steer toward a more actionable Issues backlog. If people are still encountering this in current versions (currently 3.x) please re-open this issue, open a new Issue with updated context, or raise a PR to address the problem. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#bug Bug report
Projects
None yet
Development

No branches or pull requests

2 participants