Re: Multiple versions of .... exist.

After some time of debugging I found this here: How is this possible ??? Group is still null after being set.. the same happens for version. Jorge Machado > On 12 Mar 2018, at 08:46, Jorge Machado wrote: > > Hello everyone, > > I we setting up the Nifi registry are we

Re: Multiple versions of .... exist.

Looks like a bug. The code should be: dto.setArtifact(bundle.getArtifact()); dto.setGroup(bundle.getGroup()); dto.setVersion(bundle.getVersion()); But it uses newly created dto object, instead of bundle object given as an argument. On Mon, Mar 12, 2018, 4:24 AM Jorge Machado

Multiple versions of .... exist.

Hello everyone, I we setting up the Nifi registry are we are getting this error when trying to import a flow from Registry into Nifi: Multiple versions of …. exist. No exact match for default:...:unversioned. To note that we have multiple versions of the same processor in the lib folder

Re: Multiple versions of .... exist.

Yes, I opened a PR: https://github.com/apache/nifi/pull/2531/files Jorge Machado > On 12 Mar 2018, at 09:46, Ed B wrote: > > Looks like a bug. The code should be: > > dto.setArtifact(bundle.getArtifact()); >

Re: Multiple versions of .... exist.

Nice find and thanks for the contrib/fix! Already merged. There are plenty of things in already for a release to be worthwhile. Will have the discussion on dev. Thanks On Mon, Mar 12, 2018 at 12:12 PM, Jorge Machado wrote: > Yes, > > I opened a PR:

Re: nifi unique json field list

Scott, I'm assuming you're trying to create a single (possibly sparse) table for all the incoming JSON records, and that you do not know the total set of fields ahead of time. If you do know the fields ahead of time, you can create the table ahead of time and use the JoltTransformJSON processor

Re: nifi unique json field list

Hi Scott, I am not sure why you would create a new table per file - that does not seem like a good idea to me honestly. How are going to manage these tables then? IMHO if you are on SQL Server 2016, you may consider storing json natively in SQL Server and then use various Json functions. The huge

Re: PutHiveQL (1.5.0) throws un-necessary NullPointerException when parsing the query

(dropped dev) Hi Amit, Thanks for sharing that. The parsing query is added by NIFI-4545 in NiFi 1.5.0, to parse Hive query at Hive related processors so that it can extract table names into outgoing FlowFile attributes. Those attributes are used by ReportLineageToAtlas reporting task to report

Re: nifi unique json field list

Thanks Matt and Boris for your comments/suggestions. I came to the same conclusion as Boris yesterday and put together a Groovy script. After I merge all the records into one flowfile, the Groovy script iterates through and comes up with a complete unique set of fields. I was hoping there