It might be a good idea. Though, I'm also wondering about about performance
difference between the two. Since they both use native implementations,
theoretically they can be close in performance. Are there any benchmarks
for them?
*Aleksei Statkevich *| Engineering Manager
<http://www.go
understand from the description, it should directly correspond
to CompressionHeader.NO_HEADER in ZlibCompressor. In this case,
ZlibCompressor with the right setup can be a replacement for Deflater. What
do you think?
Aleksei
*Aleksei Statkevich *| Engineering Manager
<http://www.google.com/url
Does anyone know?
*Aleksei Statkevich *| Engineering Manager
<http://www.google.com/url?q=http%3A%2F%2Frocketfuel.com%2F&sa=D&sntz=1&usg=AFrqEzfAQ9xih8SV05CiYtvyyIAKLzpX2g>
<https://www.google.com/url?q=https%3A%2F%2Ftwitter.com%2Frocketfuelinc&sa=D&sntz=1&usg=A
Hello,
I recently looked at ORC encoding and noticed that hive.ql.io.orc.ZlibCodec
uses java's java.util.zip.Deflater and not Hadoop's native ZlibCompressor.
Can someone please tell me what is the reason for it?
Also, how does performance of Deflater (which also uses native
implementation) compa
