I can see great use cases with s3/Parquet - so that's a great addition (which JB is addressing, for Java)!
It would be even more ideal for the use cases I find myself around for there to be python parquet support, so for perhaps this next release: Would it make sense to be exploring: https://arrow.apache.org ? I'd be happy to explore proper procedure for design/feature proposal and documentation for Beam, how to scope and develop it. Also, from the little I've looked at actual implementation, it appears that (py)arrow relies on underlying C binaries, which was listed as a problem or at least a point against choice of package with the developing python/kafka source. How big an issue is that -- what else should I be considering? Guidance absolutely welcomed!
