Re: java.lang.UnsatisfiedLinkError in PutHDFS with snappy compression.

Shweta, Looks like your missing the snappy native library. I have seen this several times before. Assuming your on a linux machine you have 2 options. You can copy the libsnappy.so native library to your JAVA_HOME/jre/lib native directory. Or you can set LD_LIBRARY_PATH to point to where your

Re: [GitHub] nifi pull request: NIFI-865 added initial support for AMQP publish...

David Thank you so much for reaching out. The reason why I am using RabbitMQ client library is because I am familiar with it, but as you aware AMQP is a protocol-based specification therefore it doesn’t mater which client library is used as long as they are compliant with the protocol version

Re: [GitHub] nifi pull request: NIFI-865 added initial support for AMQP publish...

I hate spell checker. The last sentence in previous response should read compliant instead of compliment. Sent from my iPhone > On Feb 6, 2016, at 17:46, Oleg Zhurakousky > wrote: > > David > > Thank you so much for reaching out. > The reason why I am using

[DISCUSS] Apache NiFi 0.5.0 RC1

Hello We put together the RC1 for nifi-0.5.0. Because we found some early bugs, as already mentioned on this list, we will not be holding a vote, but wanted to have some community feedback and testing before putting together another release candidate. The source zip, including signatures,

[GitHub] nifi pull request: NIFI-1483 - ListFile warns of unable to delete ...

GitHub user apiri opened a pull request: https://github.com/apache/nifi/pull/206 NIFI-1483 - ListFile warns of unable to delete old state when there was none Correcting logic in terms of when local persistence files are removed during the migration process. You can merge this pull

Re: [GitHub] nifi pull request: NIFI-865 added initial support for AMQP publish...

Hi Guys || This email has been sent from a virus-free computer protected by Avast. www.avast.com | As you may remember I have developed some processors that publish/subscribe to AMQP brokers, but I was having problems writing Junit tests for these processors. I was interested to see that

java.lang.UnsatisfiedLinkError in PutHDFS with snappy compression.

Hi All, I'm getting a java.lang.UnsatisfiedLinkError while adding data into PutHDFS processor with compression codec as snappy. The error message says "Failed to write to HDFS due to org.apache.hadoop.util.NativeCodeloader.build.SupportsSnappy()Z. Inspite of this error, .snappy files are being

Re: planning for apache nifi 0.5.0

Hello Would like some input/advice on https://issues.apache.org/jira/browse/NIFI-1484. In my initial testing of this I would consider it worthy of getting resolved right away. But perhaps I'm overthinking it. Related, but far less urgent, is https://issues.apache.org/jira/browse/NIFI-1483.

Does Nifi-ambari reporting supports Ambari version 2.1.1

Hi all, We are facing issue in setting up nifi service in Ambari (version 2.1.1). Getting following exception "unsupported or invalid service in stack". Just want to make sure that it is or not due to version incompatibility. Thanks, Shweta -- View this message in context:

Re: Does Nifi-ambari reporting supports Ambari version 2.1.1

Yes Joe, we followed that same document. Regards, Shweta -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/Does-Nifi-ambari-reporting-supports-Ambari-version-2-1-1-tp7178p7180.html Sent from the Apache NiFi Developer List mailing list archive at

Re: java.lang.UnsatisfiedLinkError in PutHDFS with snappy compression.

Can you show what is in your core-site.xml and the proc properties. Also can you show the full log output? Thanks Joe On Sat, Feb 6, 2016 at 9:11 AM, shweta wrote: > Hi All, > > I'm getting a java.lang.UnsatisfiedLinkError while adding data into PutHDFS > processor

Re: Does Nifi-ambari reporting supports Ambari version 2.1.1

Thanks Bryan !! that worked. Regards, Shweta -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/Does-Nifi-ambari-reporting-supports-Ambari-version-2-1-1-tp7178p7184.html Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.

Re: Does Nifi-ambari reporting supports Ambari version 2.1.1

Shweta, Have you had a chance to run through the instructions here https://cwiki.apache.org/confluence/display/NIFI/Ambari+Metrics? I also am not sure which version we support. We definitely should have that documented but it wasn't immediately obvious if we do. Bryan? Thanks Joe On Sat, Feb

Re: Does Nifi-ambari reporting supports Ambari version 2.1.1

Joe/Shweta, I view the Ambari stuff as two different pieces... the AmbariReportingTask in NiFi which was developed against Ambari 2.1, but I believe should work against any 2.X version because the Ambari Metrics Service was introduced in 2.0.0. The reporting task can send over metrics independent

[GitHub] nifi pull request: NIFI-1483 - ListFile warns of unable to delete ...

Github user trkurc commented on the pull request: https://github.com/apache/nifi/pull/206#issuecomment-180928291 @apiri - +1, works great. Only bit of weirdness, if the old state file was chmod 0400'ed (i.e., only read access) when I launched nifi, it was still deleted after

[GitHub] nifi pull request: NIFI-1483 - ListFile warns of unable to delete ...

Github user trkurc commented on the pull request: https://github.com/apache/nifi/pull/206#issuecomment-180922873 logic looks like it should cover all conditions, tests are reasonable, doing some tests --- If your project is set up for it, you can reply to this email and have your

Re: java.lang.UnsatisfiedLinkError in PutHDFS with snappy compression.

To add to Jeremy's last point, even after the library is present, the files must be greater than the HDFS block size (default is 64 MB I think?) or Hadoop-snappy will also not compress them. Sent from my iPhone > On Feb 6, 2016, at 5:41 PM, Jeremy Dyer wrote: > > Shweta, >

Re: planning for apache nifi 0.5.0

Awesome! I will start working on the rc On Feb 6, 2016 12:34 AM, "Aldrin Piri" wrote: > All, > > Just wanted to follow up that the members of the community had completed > their testing against NIFI-259 and I performed the merge of that branch > into master. > > In that