I wonder if I could get a review of this pull request
https://github.com/apache/avro/pull/1270 from the larger avro dev
community.

One thing I noticed when adding type hints to python avro is that some
of our CLI tooling supports output to standardio, but standardio is
really text, not binary. I had to relax type checking to support this
special case directly in avro.datafile and avro.io.

I think the counterpart Parquet tools would automatically output
base64-encoded binary parquet in such cases, but I'm pretty sure that
the Java avro tools does just naïvely dump binary to standard io
without any checking.

Should we change this behavior? What do you think?

Thanks,
Michael

Reply via email to