Xavier Lange

I highly recommend the `eyre` error library for applications that want rich error support. But the `eyre` says that `thiserror` is a good choice for errors you want to match...

This PR has been made worse by Kafka's bug with `lost+found` folders -- those appear in the root of all Linux filesystems. And I am using Kubernetes for it's dynamic...

Any change off of the 1+ year old JVM image would be a win. Keep in mind that the repo I use in mine is actively maintained and it drags...

Yes, you can set `ZOOKEEPER_CONNECTION_STRING`. There's an example in the README, but essentially: ``` docker run -e ZOOKEEPER_CONNECTION_STRING=zk-1:2181,zk-2:2181 $REST_OF_RUN_CMD ``` should get you going.

I can confirm the same issue on Ubuntu 12.04 x64. GHC: 7.4.1 cabal: 1.14.0 cabal-dev: 0.9.2

Those are good points. I vote for turning `get_typed_column_writer` private.

Also, the comment for `get_typed_column_writer` is from the docs for the function: ``` /// Gets a typed column writer for the specific type `T`, by "up-casting" `col_writer` of /// non-generic...

@sadikovi what do you think of this design? you mentioned you were going to work on a high-level record writer and I was curious if this design is in line...

I am very new to parquet and I'm still working through the core concepts of row group writers (columns I understand, but I guess column aren't necessarily contiguous? they go...

I think this is the relevant issue/pr pair: https://github.com/sunchao/parquet-rs/issues/116 https://github.com/sunchao/parquet-rs/pull/149