We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://clickhouse.com/docs/en/interfaces/formats#data-types-matching-arrow describes the behaviour I am observing where TIMESTAMP, TIME32, TIME64 columns are converted to UINT32 when querying in Arrow format.
I was wondering why this was done rather than mapping to native Arrow types such as date32, date64, or timestamp?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
https://clickhouse.com/docs/en/interfaces/formats#data-types-matching-arrow describes the behaviour I am observing where TIMESTAMP, TIME32, TIME64 columns are converted to UINT32 when querying in Arrow format.
I was wondering why this was done rather than mapping to native Arrow types such as date32, date64, or timestamp?
The text was updated successfully, but these errors were encountered: