Hi,   I am happy to state that after updating to CDH 5.14.4, that this crash bug seems to be fixed.  We can run Impala queries now!  This is the first we've used Impala and it looks amazingly fast - glad we can use it now 🙂  Thank you for fixing! ... View more

I received a similar error, but for the LzopCodec (not LzoCodec) not being found.  In this case, I actually wanted to use the LzoCodec as my default compression codec (for legacy reasons...).   In order to get Hive working with Lzo on CDH 5.14.x, I did the following:   1) # Add GPLEXTRAS parcel to CM and distribute to all nodes: https://www.cloudera.com/documentation/enterprise/5-14-x/topics/cm_ig_install_gpl_extras.html 2) # Configure HDFS to use it: http://www.roggr.com/2014/06/enabling-lzo-compression-for-hive-to.html ClouderaManager -> Hive -> Configuration -> Service-wide -> Advanced -> Hive Auxiliary JARs Directory : /opt/cloudera/parcels/GPLEXTRAS/lib/hadoop/lib # Verify it works by invoking 'show tables' in hive with debug-logging enabled. There should not be any errors. The error condition if not working complains about LzopCode (not LzoCodec) not found. hive --hiveconf hive.root.logger=DEBUG,console 3) # Configure HDFS ClouderaManager -> HDFS -> Configuration -> Service-wide -> Compression Codes (io.compression.codecs): + com.hadoop.compression.lzo.LzoCodec + com.hadoop.compression.lzo.LzopCodec 4) # Configure YARN/MR2 # http://blog.cloudera.com/blog/2013/07/one-engineers-experience-with-parcel/ ClouderaManager -> YARN/MR2 -> Configuration -> SearchFor: compress -> mapreduce.output.fileoutputformat.compress: checked mapreduce.output.fileoutputformat.compress.codec: com.hadoop.compression.lzo.LzoCodec mapreduce.map.output.compress: checked mapreduce.map.output.compress.codec: com.hadoop.compression.lzo.LzoCodec   ... View more

Hello,   I am running into the same problem on a fresh install of CDH 5.14.3.  According to the ticket that Tim pasted above, the issue is fixed.  Is there a timeline for when this fix will be available for general release?  Is there a workaround for this that one can utilize now?  ... View more