apache/superset

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

Open

#36.305 aberto em 27 de nov. de 2025

Ver no 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.

Guia do colaborador

Pilha de tecnologia
pythontypescript
Domain
backendfrontend
Tipo Issue
bug
DifficultyDificuldade de implementação estimada para um novo contribuidor, de 1 para alterações muito pequenas a 5 para trabalho de nível especializado.
3
Tempo estimadoUm intervalo de tempo aproximado para um colaborador experiente investigar, implementar, testar e preparar um pull request.
half day
Status da atividadeQuão disponível o issue aparece agora: novo, ativo, obsoleto, bloqueado ou aguardando entrada do mantenedor.
blocked
ClarityCom que clareza o issue explica a mudança esperada, os critérios de aceitação e a próxima etapa.
mostly clear
Prerequisites
Basic understanding of Superset's CSV importFamiliarity with Python and Flask
Simpatia para novatosUma pontuação de 1 a 100 que estima o quão acessível este issue é para colaboradores iniciantes.
40
Direção de pesquisa
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.