Option 2: You can use the RouteOnAttribute processor to filter out FlowFiles with null values using the expression language ${externalId:isNull()} and route them to the next processor. ... View more

Hi @Thar11027 , Can you try something like this below. Thanks, ... View more

Hello, We you can try something like this. Step 1 : Add an InvokeHTTP Processor to Generate the Token Step 2: Extract Token Using EvaluateJsonPath Processor: Step 3: Use the Token in a InvokeHTTP Thanks, ... View more

Transferring Data from Multiple Tables in NiFi: NiFi provides processors that allow you to pull data from database tables using JDBC drivers. For Oracle, you can use processors like ExecuteSQL, QueryDatabaseTable, and GenerateTableFetch. To transfer data from multiple tables, consider the following approaches: Individual Flows for Each Table: You can create separate NiFi flows for each table. This approach is straightforward but may require more management. Dynamic SQL Generation: Use the ListDatabaseTables processor to list tables dynamically. Then, use ReplaceText to create SQL statements for each table (using NiFi Expression Language). Finally, send these statements to ExecuteSQL for fetching data. Parallel Fetching: If you have a NiFi cluster, route GenerateTableFetch into a Remote Process Group pointing at an Input Port on the same cluster.  Automatic Table Creation in Cassandra Using Avro Schemas: To create tables in Cassandra, you can use the PutCassandraRecord processor. It allows you to put data directly into Cassandra without writing CQL. For schema management, consider using Avro schemas. You can define Avro schemas for your data and use them within your NiFi flow. To handle overwriting tables, you’ll need to manage the logic in your flow.  Can Nifi load data from DB2 to Cassandra? - Stack Overflow   ... View more

Hello, You can use the executeSql processor to read the data and if you put the putdatabaserecord processor to insert the data into oracle database. you don't need to convert the records, just define the input processor as avro reader. ... View more

Ideally, it should return the current date minus 24 hours and convert it to a specific time zone. Please check your server time.   CET: ${now():toNumber():minus(86400000):format('yyyy-MM-dd HH:mm:ss', 'CET')} GMT: ${now():toNumber():minus(86400000):format('yyyy-MM-dd HH:mm:ss', 'GMT')} Midnight CET: ${now():toNumber():minus(86400000):format('yyyy-MM-dd', 'CET'):append(' 00:00:00')} Thanks ... View more

I believe we can determine this by analyzing the log. For instance, if a job is stuck in a queue, we can check the log for specific statuses such as "suspended" or "wait." If such statuses are found, we can trigger an email notification. ... View more

How to Resolve SNI issue when upgrading to NiFi 2.0 https://medium.com/@chnzhoujun/how-to-resolve-sni-issue-when-upgrading-to-nifi-2-0-907e07d465c5#:~:text=Due%20to%20the%20upgrade%20to,400%3A%20Invalid%20SNI%20will%20occur ... View more

Thank you, @SAMSAL. This logic is much simpler. My JOLT logic was a bit complex. This is going to save me a lot of time. Is there are any tutorial where we can learn the JOLT ? ... View more

Just to give a heads up, my input will be something like the example below. I have around 60 columns, and out of those, only 4 columns are in the list. Example: from below example i would like to handle the "DEFECT_ROOT_CAUSE" and "SPRINT_LIST"  Output would be same as your solution: DEFECT_ROOT_CAUSE:"Frontend" SPRINT_LIST:"24-w2-3"     ================================== -- input 1 ================================== [ { "INTEGRATION_ID" : "1111", "ISSUE_KEY" : "PP2-7426", "SUMMARY" : "Confirmation Web", "SPRINT_LIST" :"24-w2-1", "DEFECT_TYPE" : "poor user interface design, confusing navigation", "TEAM" : "Web Engineering", "PLATFORM" : "Customer Web", "DEFECT_ROOT_CAUSE" : [ "Backend", "Frontend" ] } ] ================================== -- input 2 ================================== [ { "INTEGRATION_ID" : "2222", "ISSUE_KEY" : "PP2-7427", "SUMMARY" : "Confirmation Web", "SPRINT_LIST" : [ "24-w2-1", "24-w2-2", "24-w2-3" ], "DEFECT_TYPE" : "poor user interface design, confusing navigation", "TEAM" : "Web Engineering", "PLATFORM" : "Customer Web", "DEFECT_ROOT_CAUSE" : "Backend" } ]   ... View more