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

How should values of DuckDB's HUGEINT be cast to an Iceberg type? #2

Closed
ghalimi opened this issue Jan 21, 2023 · 3 comments
Closed
Labels
question Further information is requested

Comments

@ghalimi
Copy link
Contributor

ghalimi commented Jan 21, 2023

DuckDB supports the HUGEINT type for signed sixteen-byte integers, but Apache Iceberg does not. How should values of this type be cast? A pragmatic option would be to use long 64-bit signed integers, but this would result in significant loss of information. Assuming this is acceptable, what should be done with values that are out of bounds? Otherwise, which alternative options should be considered?

Link: Types

@ghalimi ghalimi added the question Further information is requested label Jan 21, 2023
@ghalimi
Copy link
Contributor Author

ghalimi commented Jan 23, 2023

This is probably not urgent.

@ghalimi ghalimi closed this as completed Jan 23, 2023
@alexey-milovidov
Copy link

ClickHouse had the same question when we added the integration with external databases (MySQL, Postgres, etc.), and the obvious solution is to fall back to the String data type.

@ghalimi
Copy link
Contributor Author

ghalimi commented Mar 22, 2023

That could be an option indeed. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants