alamb commented on issue #5854: URL: https://github.com/apache/arrow-rs/issues/5854#issuecomment-2159096227
> I would love to get some feedback on the code, and whether there would be a preference to integrate the parquet definitions into the arrow-rs repo, or publish them separately. Hi @jhorstmann -- I had a look at https://github.com/jhorstmann/compact-thrift/tree/main (very cool) Some initial reactions: Writing a code generator in Kotlin is a neat idea, but I think it might make the barrier to contribution high (now people need to know Rust and Kotlin (and the associated toolchains, etc) Also, I keep thinking if we are going to have a parquet-rs specific implementation, why use a code generator at all? Maybe we could simply hand code a decoder directly that uses the runtime library Given how infrequently the parquet spec changes, a hand rolled parser might be reasonable (though I will admin that the [generated format.rs](https://github.com/jhorstmann/compact-thrift/blob/main/src/main/rust/parquet/src/format.rs) is substantial 🤔 ). We can probably ensure compatibility with round trip testing of generated rust code 🤔 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
