question Re: Enabling LZO compression using NiFi PutHDFS in Archives of Support Questions (Read Only)

Enabling LZO compression using NiFi PutHDFS

arunak — Sat, 10 Dec 2016 06:09:32 GMT

Hello All,

LZO compression codec is enabled on HDFS and we are writing to HDFS using PutHDFS. We have run into the issue as in this question. Workaround to remove the LZO specific line from the core-site works fine. However, is there a way that we can still use LZO codec with NiFi PutHDFS. The compression codec section of this document does not have specifics around NONE, AUTOMATIC and DEFAULT. Could someone share more information around this?

Thanks, Arun

Re: Enabling LZO compression using NiFi PutHDFS

knarayanan — Tue, 13 Dec 2016 03:08:37 GMT

you will have to include the path to lzo codec binaries in the NiFi bootstrap script.

add an entry like so -

java.arg.15=-Djava.libaray.path=/path/to/your/lzocodec.so in the bootstrap.conf file.

Re: Enabling LZO compression using NiFi PutHDFS

arunak — Tue, 13 Dec 2016 04:50:33 GMT

Thanks @Karthik Narayanan, yet to try this, could you also help on the compression codec to be used in this case? I haven't been able to find out what NONE, AUTOMATIC and DEFAULT means.

Re: Enabling LZO compression using NiFi PutHDFS

bbende — Tue, 13 Dec 2016 05:55:18 GMT

NONE means don't use a codec at all.

AUTOMATIC is not meant to be used with PutHDFS, it is only for the read side (GetHDFS and FetchHDFS)

DEFAULT means use the DefaultCodec class provided by Hadoop which I believe uses a zlib compression (slide 6 here http://www.slideshare.net/Hadoop_Summit/kamat-singh-june27425pmroom210cv2)

Re: Enabling LZO compression using NiFi PutHDFS

arunak — Wed, 14 Dec 2016 02:20:33 GMT

@Karthik Narayanan : Just to give you an update, this did not work for me. Tried the same with Snappy. Even snappy does not seem to work. Throws an unsatisfied link even though I have the ".so" added to the bootstrap.conf

Re: Enabling LZO compression using NiFi PutHDFS

knarayanan — Wed, 14 Dec 2016 08:35:01 GMT

any chance you are on OS X?

Re: Enabling LZO compression using NiFi PutHDFS

arunak — Thu, 15 Dec 2016 22:30:43 GMT

Nope, its on the ambari vagrant box

Re: Enabling LZO compression using NiFi PutHDFS

knarayanan — Thu, 15 Dec 2016 23:38:08 GMT

https://community.hortonworks.com/articles/71719/using-snappy-and-other-compressions-with-nifi-hdfs....

I posted the above link on how you can use compression, try and let me know how it goes. I don't think you can use LZO as it is not shipped as part of Nifi. You can try doing a yum install of LZO and then use executestream to compress the file and then do puthdfs, with none for compression codec.

Re: Enabling LZO compression using NiFi PutHDFS

arunak — Sun, 18 Aug 2019 13:20:28 GMT

Thanks @Karthik Narayanan. I was able to resolve the issue.

Before diving into the solutions, I should make the below statement -

With NiFi 1.0 and 1.1, LZO compression cannot be achieved using the PutHDFS processor. The only supported compressions are the ones listed in the compression codec drop down.

With the LZO related classes being present in the core-site.xml, the NiFi processor fails to run. The suggestion from the previous HCC post was to remove those classes. It needed to be retained so that NiFi's copy and HDP's copy of core-site are always in sync.

NiFi 1.0

I created the hadoop-lzo jar by building it from sources and added the same to the NiFi lib directory and restarted NiFi.

This resolved the issue and I am able to proceed using the PutHDFS without it erroring out.

NiFi 1.1

Configure the processor's additional classpath to the jar file. No restart required.

Note : This does not provide LZO compression, it just can run the processor without ERROR even when you have the LZO classes in the core site.

UNSATISFIED LINK ERROR WITH SNAPPY

I also had issue with Snappy Compression codec in NiFi. Was able to resolve it setting the path to the .so file. This did not work on the ambari-vagrant boxes, but I was able to get this working on an openstack cloud instance. The issue on the virtual box could be systemic.

To resolve the link error, I copied the .so files from HDP cluster and recreated the links. And as @Karthik Narayanan suggested, added the java library path to the directory containing the .so files.

Below is the list of .so and links

And below is the bootstrap configuration change