apache/superset

Import CSV ; The "schema" field required or not --> 2 datasets for 1 table

Open

#36305 opened on Nov 27, 2025

View on GitHub
 (12 comments) (0 reactions) (1 assignee)TypeScript (72,837 stars) (17,291 forks)batch import
data:csvgood first issuevalidation:required

Description

Bug description

Description

The "schema" field is not required :

with version 4 value 'public' was set by default but with V5.0.0, the default value is not set

The error message should precise

The import is OK if user set a schema but 2 datasets are existing for 1 table

Screenshots/recordings

No response

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.

Contributor guide

Tech stack
pythontypescript
Domain
backendfrontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic understanding of Superset's CSV importFamiliarity with Python and Flask
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the CSV import logic in Superset's backend, likely in the superset/datasets/commands/importers/ directory. Focus on how the 'schema' field is handled when not provided; ensure a default value (e.g., 'public') is set. Also, check the error message generation to provide a more precise message when two datasets result for one table. Review related test files for import behavior.