Core: Improve error for null/unknown schema types in table creation #2843

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.

Sign up for GitHub

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

Jump to bottom

Open

010Soham wants to merge 1 commit into apache:main from 010Soham:fix-2539-null-type-error

010Soham commented Dec 19, 2025

What changed

Add a client-side validation error when a PyArrow null type is used with format version < 3, including the field path and a hint to use a concrete type or format-version 3.
Add a unit test to verify the clear error message when converting a PyArrow schema with a null field.

Why

Prevents misleading REST errors like “Cannot parse type string… unknown” and points directly to the offending field.

Testing

make lint
uv run pytest tests/catalog/test_base.py -k rejects_null_type -v
make test (timed out at ~42%)

Closes #2539


          Core: improve error for null schema types

e8b7fa6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet