Skip to content
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

🐛 Bug: Mixed case column names from Source S3 is causing empty data when loaded to DuckDB #108

Closed
divyagowdab opened this issue Mar 7, 2024 · 2 comments · Fixed by #114
Assignees

Comments

@divyagowdab
Copy link

divyagowdab commented Mar 7, 2024

I tried to read data from a s3 source. The bucket had one csv file. Attached the sample csv file.
In the attached file there are 2 colums starting with upper case (Age and Credit_rating). For those 2 columns the duck db does not have data. (attached screenshot)
If i change all the column names to lower case then everything works fine.
And also if the column names are hyphen separated then "missing column" error is thrown.
TestData.csv
Screenshot 2024-03-08 at 1 43 47 AM

@aaronsteers
Copy link
Contributor

@divyagowdab - This is very helpful feedback - thank you.

We will see if I can reproduce this using the File source, and will report back.

@aaronsteers aaronsteers changed the title If the column names in the data source are not in lower case then the data inserted in duckdb will be empty 🐛 Bug: Mixed case column names in S3 source results in empty data when loaded to DuckDB Mar 7, 2024
@aaronsteers aaronsteers changed the title 🐛 Bug: Mixed case column names in S3 source results in empty data when loaded to DuckDB 🐛 Bug: Mixed case column names from Source S3 is causing empty data when loaded to DuckDB Mar 7, 2024
@aaronsteers
Copy link
Contributor

@divyagowdab - We have a PR ready for review, which should resolve this: #114

@aaronsteers aaronsteers self-assigned this Mar 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment