File and column descriptions from dataset-metadata.json are still not saved (after #1055)
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 45/100
Línea de trabajo
Start with docs/datasets_metadata.md and trace datasets create, datasets version, and metadata --update through DatasetApiService.UpdateDatasetMetadata. Reproduce with the supplied dataset-metadata.json, inspect GetDatasetMetadata, and verify that file and column descriptions survive each command and appear in the Data Explorer.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
File and column descriptions in dataset-metadata.json are accepted without error but never saved. This happens on datasets create, datasets version and datasets metadata --update. #447 and #248 were closed by #1055, but that PR changed only how the CLI builds the request. The server still drops the descriptions. Descriptions entered in the web editor are saved as expected.
The documentation says this should work:
- docs/datasets_metadata.md lists
resources(withpath,descriptionandschema.fields[].description) as supported forkaggle datasets createandkaggle datasets version. - The same page says
kaggle datasets metadata --update"supports all fields mentioned above forkaggle datasets version".
Environment
- kaggle 2.2.4, kagglesdk 0.1.37
- Python 3.14.3, Ubuntu (GitHub Actions
ubuntu-latest) - Authenticated with
KAGGLE_API_TOKEN
Steps to reproduce
-
Make a folder with
data.csv:year,category,grants 1977-78,Refugee,9326 1978-79,Refugee,12750 -
Add
dataset-metadata.jsonbeside it, following the documented format:{ "title": "Metadata description test", "id": "<your-username>/metadata-description-test", "licenses": [{"name": "CC0-1.0"}], "resources": [ { "path": "data.csv", "description": "Rows of the table, as CSV.", "schema": { "fields": [ {"name": "year", "description": "Financial year.", "type": "string"}, {"name": "category", "description": "Visa category.", "type": "string"}, {"name": "grants", "description": "Visas granted.", "type": "number"} ] } } ] } -
Create the dataset, wait until it is ready, then upload the same files as a new version:
kaggle datasets create -p . -u kaggle datasets status <your-username>/metadata-description-test # until "ready" kaggle datasets version -p . -m "second version with the same resources" -
Send the same file again as a metadata update:
kaggle datasets metadata <your-username>/metadata-description-test --update -p . -
Open the dataset page and select
data.csvin the Data Explorer.
Expected
"About this file" shows "Rows of the table, as CSV.", and each column shows its description. The usability rating ticks File Description and Column Description.
Actual
- "About this file" says "This file does not have a description yet", and no column has a description.
- The usability rating still crosses File Description and Column Description.
- Every command exits 0.
metadata --updateprints "successfully updated dataset metadata". - The other fields in the same update are saved: keywords,
expectedUpdateFrequency,userSpecifiedSourcesand the cover image.
What else we tried
All of these were accepted with an empty errors list, and none changed the page:
resourceswith the documented types (string,number,datetime), and withinteger.- Calling
DatasetApiService.UpdateDatasetMetadatathrough kagglesdk directly, withsettings.dataset toDatasetSettingsFileentries in four forms: description only; description andtotalBytes; those pluscolumns; and all three files of the dataset. - Three dataset versions uploaded with
resourcespresent (createonce, thenversiontwice).
GetDatasetMetadata returns info.data as an empty list after each update, as #410 also notes.
Example
A public dataset that shows the problem: https://www.kaggle.com/datasets/nationaldigitalau/au-humanitarian-program-grants. Version 3 was uploaded with resources for all three files and then sent the same settings through metadata --update.
- Lenguaje dominante
- Python
- Estrellas
- 7.7k
- Forks
- 1.5k
- Merge medio
- 1 d 6 h
- PR fusionados (30 d)
- 17
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Kaggle/kaggle-cli
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Kaggle/kaggle-cli#1254 ·
Los mantenedores suelen responder en 1 día
-
duplicate
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
Kaggle/kaggle-cli#1248 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
datasets metadata --update crops cover images larger than 560x280 to their top-left cornerPosiblemente ocupada @tb91117 la tomó hoy. Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 55/100
Kaggle/kaggle-cli#1250 ·
Los mantenedores suelen responder en 1 día
-
bug dependencies
Dificultad 3/5 1-2 días Aptitud para principiantes 52/100
Kaggle/kaggle-cli#1229 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 Menos de una hora Aptitud para principiantes 50/100
Kaggle/kaggle-cli#1217 ·
Los mantenedores suelen responder en 1 día
Todos los issues de Kaggle/kaggle-cli
Issues similares
-
documentation
Dificultad 1/5 Menos de una hora Aptitud para principiantes 74/100
BrainLesion/BraTS#200 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
OpenHands/extensions#970 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
rl-institut/enetra#91 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
huggingface/datasets#9100 ·
Los mantenedores suelen responder en 1 día
-
needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
NVIDIA/garak#2486 · 1 comentario ·
Los mantenedores suelen responder en 2 días