Replies: 1 comment
-
Yes, adding arrays would be great as I am using arrays to handle very large volumes of time series data. In my case, I store the data with a date and then a fixed size array to represent metric for each period in the day. i.e. 96 entry arrays for 15m frequency. The idea is that I can do fast aggregations by dimensional values of the time series etc... My ultimate goal would be to have access to vectorized calculations (such as entrywise sum, entrywise multiplication, array * scalar etc...) directly with sql functions. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Similarly to the #32 which says support for geospatial will be added, I'd argue that Arrays are a fundamental type within duckdb and it would be very appropriate to have support within ducklake.
This could probably be added in a similar way to Json being added.
While arrays aren't a raw part of the default parquet datatypes, neither is json
Beta Was this translation helpful? Give feedback.
All reactions