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

Add support for int8/16 to parquet encode #147

Merged
merged 5 commits into from
Oct 30, 2024
Merged

Conversation

richardartoul
Copy link
Contributor

No description provided.

case int16:
field.SetFloat(float64(v))
case int32:
field.SetFloat(float64(v))
case int64:
field.SetFloat(float64(v))

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is int64 to float 32 lossy?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

definitely lossy, but wont underflow/overflow

case float32:
field.SetFloat(float64(v))
case float64:
field.SetFloat(v)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this lossy? Or is the float32 field just stored as float64

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think so, but would have to be a humongous number. We can fix this later if it comes up, thats how it worked before

@richardartoul richardartoul merged commit 7b10c77 into main Oct 30, 2024
3 checks passed
@richardartoul richardartoul deleted the feat/int-types branch October 30, 2024 20:42
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