Re: PutHDFS with mapr

> > > Thanks, > > Ravi Papisetti > > > > From: Andre <andre-li...@fucs.org> > Reply-To: "andre-li...@fucs.org" <andre-li...@fucs.org> > Date: Tuesday, 27 March 2018 at 8:27 PM > To: Cisco Employee <rpapi...@cisco.com> > Cc: &qu

Re: PutHDFS with mapr

quot;andre-li...@fucs.org" <andre-li...@fucs.org> Subject: Re: PutHDFS with mapr Ravi, I assume the MapR client package is working and operational and you can login to the uid running NiFi and issues the following successfuly: $ maprlogin authtest $ maprlogin print $ hdfs dfs -ls

Re: PutHDFS with mapr

resetHDFSResources(AbstractHadoopProcessor.java:281) > > at org.apache.nifi.processors.hadoop.AbstractHadoopProcessor. > abstractOnScheduled(AbstractHadoopProcessor.java:205) > > > > Thanks, > > Ravi Papisetti > > > > > > *From: *Andre <andre-li

Re: PutHDFS with mapr

"andre-li...@fucs.org" <andre-li...@fucs.org> Date: Sunday, 25 March 2018 at 3:56 PM To: "users@nifi.apache.org" <users@nifi.apache.org> Subject: Re: PutHDFS with mapr Joey, Yes. The client must be installed and setup (this is a requirement for the compiled NiFi

Re: PutHDFS with mapr

s.org> Date: Sunday, 25 March 2018 at 9:34 PM To: Cisco Employee <rpapi...@cisco.com> Cc: "users@nifi.apache.org" <users@nifi.apache.org>, "andre-li...@fucs.org" <andre-li...@fucs.org> Subject: Re: PutHDFS with mapr Ravi, Have you tried without recompi

Re: PutHDFS with mapr

ot;users@nifi.apache.org" <users@nifi.apache.org>, " > andre-li...@fucs.org" <andre-li...@fucs.org> > *Date: *Sunday, 25 March 2018 at 3:56 PM > *To: *"users@nifi.apache.org" <users@nifi.apache.org> > *Subject: *Re: PutHDFS with mapr > > &g

Re: PutHDFS with mapr

he.org>, "andre-li...@fucs.org" <andre-li...@fucs.org> Date: Sunday, 25 March 2018 at 3:56 PM To: "users@nifi.apache.org" <users@nifi.apache.org> Subject: Re: PutHDFS with mapr Joey, Yes. The client must be installed and setup (this is a requirement for the

Re: PutHDFS with mapr

Joey, Yes. The client must be installed and setup (this is a requirement for the compiled NiFi as well). Without the client installed and configured the MapR libraries (java and native) would be lost in to what ZK connect in order to get information about the CLDB (their alternative to

Re: PutHDFS with mapr

I'm kinda going on memory here because I lost some notes I had about doing this, but I think the compile against the mapr libs presumes you have also have the C-based mapr client libs on your machine at compile time and run time. I skimmed that blog post, albeit very quickly, and didn't see

Re: PutHDFS with mapr

Andre, I knew this was possible but had no idea how. Thanks for the great explanation and associates caveats! -Mark On Mar 24, 2018, at 1:04 AM, Andre > wrote: Ravi, There are two ways of solving this. One of them (suggested to me MapR

Re: PutHDFS with mapr

Ravi, There are two ways of solving this. One of them (suggested to me MapR representatives) is to deploy MapR's FUSE client to your NiFi nodes, use the PutFile processor instead of PutHDFS and let the MapR client pump coordinate the API engagement with MapR-FS. This is a very clean and robust

PutHDFS with mapr

Hi, I have re-compiled nifi with mapr dependencies as per instructions at http://hariology.com/integrating-mapr-fs-and-apache-nifi/ Created process flow with ListFile > FetchFile > PutHDFS. As soon as I start this process group nifi-bootstrap.log is getting filled with 2018-03-21 22:56:26,806