Matt, Yeah, I saw that pretty early on. Admittedly my question may be a bit nebulous. What I'm trying to figure out is what I should be seeing in Atlas if NiFi is sending it events properly. Since the integration and knowledge around it is probably clustered here, I'm not sure I can go to the Atlas list and ask them the same question.
Thanks, Mike On Wed, Feb 28, 2018 at 2:13 PM, Matt Burgess <[email protected]> wrote: > Mike, > > There is a nifi-atlas-bundle in NiFi with a NAR that includes the > ReportLineageToAtlas reporting task, but IIRC it is so large that it > is not included in the default assembly. Instead there is a > "include-atlas" profile that can be activated when building the > assembly, and that should include the Atlas NAR and associated > reporting task. > > Regards, > Matt > > > On Wed, Feb 28, 2018 at 1:42 PM, Mike Thomsen <[email protected]> > wrote: > > I have Atlas 0.8.2 (BerkeleyDB and Embedded ES) and NiFi 1.6.0 nightly > both > > up and claiming that they can talk to one another. > > > > What should I be seeing if they are? My test configuration consists of a > > simple process group that has GetMongo, UpdateAttributes and > > PutElasticSearchHttpRecord. I'm not sure if events are actually making > it. > > > > The Atlas documentation is pretty limited on setting up a vanilla > > installation, so I was wondering if someone could point me in the right > > direction from a NiFi point of view on what I should be seeing so I can > > start fumbling around in the right direction. > > > > Thanks, > > > > Mike >
