Skip to content

Attempting to replicate avro field name issue with DuckDB #2243

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.

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

Closed
wants to merge 1 commit into from

Conversation

sungwy
Copy link
Collaborator

@sungwy sungwy commented Jul 23, 2025

Attempting to replicate the issue reported in #2123

@sungwy
Copy link
Collaborator Author

sungwy commented Jul 23, 2025

@nvartolomei - I'm attempting to replicated the issue you've reported with the exact same schema and partition spec, but I am able to read the table just fine using duckdb. Are you able to demonstrate how to replicate the issue?

@nvartolomei
Copy link

@sungwy what DuckDB version is used in tests? My example was run with 1.3.1. Before that (don’t know the exact version number), duckdb had a different implementation had more relaxed constraints on inputs.

@kevinjqliu
Copy link
Contributor

the latest duckdb version is used in test, so 1.3.1
i tried with older versino of duckdb kevinjqliu#16 and could not reproduce the error

@kevinjqliu
Copy link
Contributor

closing this, original issue was fixed in #2245

@kevinjqliu kevinjqliu closed this Aug 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants