About justenji

justenji · ‎12-07-2020

@ang_coder The AvroSchemaRegistry is to set in the ControllerServices. If it should be available in your whole NiFi just go to the canvas and click anywhere right -> choose "Configure". It is the same place where you define your database connections. Configure -> ControllerServices If you already have JSON-format just ignore the first two steps of my example flow where data were retrieved and converted to JSON. Start with your JSON at UpdateAttribute which doesn't care about the kind of flowfile content. The ConvertRecord in my example uses an JSON-reader and JSON-writer where the writer points to the AvroSchemaRegistry with the schema.name set in UpdateAttribute. Therefore the JsonRecordSetWriter_IJ_TestMoreColumnsAtTarget (just to take a short name) has the specification "Schema Access Strategy" with option "Use Schema.Name Property". Have a look at the configuration details in my post before. Hope this helps.

justenji · ‎12-06-2020

@dzbeda Try it with: /*:Event/*:System/*:Channel

justenji · ‎12-04-2020

@ang_coder Tried it myself and have to correct my idea a little bit. Have a look at my example. Here are my tables. The target table has two columns more than the source. Tables I defined following ControllerServices: ControllerServices And created this flow: Flow Here the information of the single processors: Processor information In my example it works. Sure there will be a more elegant solution but I don't know how.

justenji · ‎12-04-2020

@ang_coder I'm not sure if i get you right and haven't done such a thing myselfe until now. But if you use PutDatabaseRecord instead of PutSQL you have to specify a RecordReader. This will be configured as ControllerService and you can add a schema in AvroSchemaRegistry (also in ControllerServices). In this schema provide the full table definition with default values. f.e. { "name" : "zeichen", "type" : ["string","null"] },... I suppose that all columns which are not included by your flowfile should be taken from the schema considering the default values.

justenji · ‎12-03-2020

@stephane_davy Sorry, my above picture is a kind of vision test... Flow and Step1 and 2 Step 3 Rule 1 Step 3 Rule 2 Step 4

justenji · ‎12-03-2020

@stephane_davy Maybe you want to give this solution a try? Hope the explanation is clear. If not feel free to ask again. <Picture removed>

justenji · ‎11-02-2020

@kumar79 Maybe you could reset the state via NiFi-REST-API at beginning of your flow? Hava a look here: https://nifi.apache.org/docs/nifi-docs/rest-api/index.html Could be: POST "https://[ip:port]/nifi-api/processors/${pg-id}/state/clear-requests" This is the request which NiFi itself uses when you go to the processor in the UI and choose the menu-option "view state" -> "clear state".

justenji · ‎10-26-2020

@MKS_AWS You can do this in different ways. Possibility 1 Create variables in VariableRegistry containing your authorization data. Possibility 2 Create a parameter list and define your authorization data there in parameters. In both ways you can use the variables or parameters inside the InvokeHTTP. Here an example with variables. If you get your authorization data from a database table just set them into attributes and use them in the same way.

justenji · ‎10-15-2020

Thanks for your help @ashinde ! I see I was looking at the wrong section of rest-api. OK I have to go on nifi rest-api section flow/history. I will have a look on the nifi.properties but because my report is running every night I suppose the purging doesn't matter. Second option you mentioned concerning when a flow was brought to registry doesn't interest... at the moment.

justenji · ‎10-14-2020

@ashinde Thanks for this information. Tested the command with InvokeHTTP from NiFi itselfe. So I would have to deliver a list of Processgroup-IDs to check with this request... At the moment I try getting information with https://${hostname(true)}:${NIFI_PORT}/nifi-api/process-groups/${PG_ID}/process-groups starting with root-pg-id, split and doing the same for each therein found processgroup in a loop. So I can get component-name, component-version, pg-id. One info I still miss is timestamp when a processgroup was brought to a NiFi-instance (imported from registry) or when it was last updated (change of version). Do you have a tip where to find this? Thanks.

Online	Offline
Last Visited	‎07-13-2021 11:50 PM

Member Since	‎09-27-2018 05:54 PM
Last Visited	‎07-13-2021 11:50 PM
Posts	138
Kudos received	23

Cloudera Community

Re: How to extract json array using EvaluateJsonPa...

Re: NiFi CLI Tookit : set-param

Re: NiFi InvokeHTTP POST JSON

Re: How to track the Nifi procssors success or err...

Re: [Nifi] - Multiple predicate in recordpath filt...

Re: ConvertJSONtoSQL Issue: How to get unmatched C...

Re: Nifi - Extract value from XML content and add ...

Re: ConvertJSONtoSQL Issue: How to get unmatched C...

Re: ConvertJSONtoSQL Issue: How to get unmatched C...

Re: [Nifi] - Multiple predicate in recordpath filt...

Re: [Nifi] - Multiple predicate in recordpath filt...

Re: Adding sequence Number to filename

Re: InvokeHTTP

Re: NiFi - REST-API - searching for information ab...

Re: NiFi - REST-API - searching for information ab...