You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 11, 2021. It is now read-only.
If users write to their parquet files through an intermediate struct, we can help them out by generating the parquet schema from the struct.
I like to model rows of my parquet file using structs, for example:
and then I have to manually track the schema, writing something by hand like:
and any time I make a change to the
PurchaseOrderRecord
I have to manually updatepurchase_orders_schema
or else I get runtime errors.We can avoid this whole situation by providing a deriving procedural macro. I was thinking something name
ParquetSchema
, to be used:which would derive a value and an accessor trait. With the macro fully expanded you would get something like:
what's interesting here is that I can build the concrete schema enum at compile time.
This functionality would remove error prone steps for writers/schemas. This is a big pain point for me 😄.
The dream would be to enable functionality like:
and then users can focus on their data and the parquet stuff is taken care of!
Also, I glossed it over, but we may want some kind of schema accessor trait to map a struct type to the macro-generated static schema type enum:
which would allow the user to access the schema anywhere with:
The text was updated successfully, but these errors were encountered: