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.

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

[BUG] Can't use numbers in parquet column names #387

Closed
CeciliaCoelho opened this issue May 21, 2021 · 1 comment
Closed

[BUG] Can't use numbers in parquet column names #387

CeciliaCoelho opened this issue May 21, 2021 · 1 comment

Comments

@CeciliaCoelho
Copy link

If I have a column names 1_A, 2_A, etc the Schema ("Schema."+strconv.Itoa(1)+"A") doesn't work for some reason but if I change the order of the name components to A_1, A_2, etc it works perfectly using "Schema.A_"+strconv.Itoa(1). Is this a bug?
@hangxie
Copy link
Contributor

hangxie commented Jun 11, 2021

This is by design, schema that does not start with alphabetic characters will be prefixed by PARGO_PREFIX, it's mentioned in the README, you can also reference to #294.

@D3Hunter D3Hunter mentioned this issue Aug 9, 2022
Closed
zolstein pushed a commit to zolstein/parquet-go that referenced this issue Jun 23, 2023
Refactor assigning Parquet values to Go values (xitongsys#387)
5337127 
As part of exploring xitongsys#266, it was identified that the code around
deserializing Parquet values into Go values should be refactored to make
supporting other types like `time.Time` possible. This is the first
change which refactors the monolithic `assignValue()` function into an
`AssignValue()` function implemented on each Parquet type.
@hangxie hangxie mentioned this issue Nov 17, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hangxie @xitongsys @CeciliaCoelho