fix!: Use an arrow date type for clickhouse dates #18914
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm not sure what the reasoning was behind representing clickhouse Date as a string.
However, for me it resulted in a panic when using the clickhouse source:
Seems more appropriate to use the same type that is used to represent Date32.
https://clickhouse.com/docs/en/sql-reference/data-types/date
https://clickhouse.com/docs/en/sql-reference/data-types/date32
An alternative fix that wouldn't require changing arrow types would be to modify
cloudquery/plugins/destination/clickhouse/typeconv/arrow/values/values.go
Line 45 in 3ae9b11
buildFromStringinstead ofbuildPrimitive.