while running run_qa.py, ran into a value error

command:

python3 run_qa.py   --model_name_or_path hyunwoongko/kobart    --dataset_name squad_kor_v2   --do_train   --do_eval   --per_device_train_batch_size 8   --learning_rate 3e-5   --num_train_epochs 3   --max_seq_length 512   --doc_stride 128   --output_dir /tmp/debug_squad/

error: 

ValueError: External features info don't match the dataset:
Got
{'id': Value(dtype='string', id=None), 'title': Value(dtype='string', id=None), 'context': Value(dtype='string', id=None), 'question': Value(dtype='string', id=None), 'answer': {'text': Value(dtype='string', id=None), 'answer_start': Value(dtype='int32', id=None), 'html_answer_start': Value(dtype='int32', id=None)}, 'url': Value(dtype='string', id=None), 'raw_html': Value(dtype='string', id=None)}
with type
struct<answer: struct<text: string, answer_start: int32, html_answer_start: int32>, context: string, id: string, question: string, raw_html: string, title: string, url: string>

but expected something like
{'answer': {'answer_start': Value(dtype='int32', id=None), 'html_answer_start': Value(dtype='int32', id=None), 'text': Value(dtype='string', id=None)}, 'context': Value(dtype='string', id=None), 'id': Value(dtype='string', id=None), 'question': Value(dtype='string', id=None), 'raw_html': Value(dtype='string', id=None), 'title': Value(dtype='string', id=None), 'url': Value(dtype='string', id=None)}
with type
struct<answer: struct<answer_start: int32, html_answer_start: int32, text: string>, context: string, id: string, question: string, raw_html: string, title: string, url: string>

I didn't encounter this error 4 hours ago. any solutions for this kind of issue?
looks like gained dataset format refers to 'Data Fields', while expected refers to 'Data Instances'.


Hi! Triaging older issues this week — I couldn't reproduce this on the current `main` (datasets 4.8.6.dev0).

The error reported here is `ValueError: External features info don't match the dataset` from running `run_qa.py` on `squad_kor_v2`. Two reasons this likely doesn't reproduce today:

- `squad_kor_v2` was a script-based loader (no `squad_kor_v2/` directory in this repo anymore). `src/datasets/load.py:1661-1666` shows `load_dataset` no longer supports loading scripts; the dataset, if still available, is now Parquet-backed on the Hub and the feature schema is fixed at upload time rather than reconstructed dynamically.
- The "External features info don't match the dataset" path in `arrow_dataset.py` is the schema-coercion check, and it now operates over Arrow tables that come from a single source of truth (the Hub Parquet) rather than from a freshly-executed Python builder, so the struct-ordering mismatch you ran into is much less likely.

The reporter also notes "I didn't encounter this error 4 hours ago" — consistent with a transient upstream loader change at the time, not a current bug.

If a comparable schema mismatch still happens on a recent release, a minimal repro (versions, exact `load_dataset` call, traceback) would help. Otherwise I'd suggest closing — happy to be wrong if I missed something.

(Disclosure: I drafted this comment with help from Claude Code while triaging stale issues; the references above were verified manually against the current `main` branch at commit 19302564.)