Is there anything in the logs before/after the "already marked for transfer" entry? Trying to figure out how a flow file can get transferred and then something goes wrong (where we'd try to also send it to failure) ... View more

@mburgess Helpful information shared. I am using Nifi 1.7.1 For my case, the incremental fetching does not seem to work correctly. All records gets ingested from the database but do not make it all the way to the destination. Processor used is GenerateTableFetch then Execute SQL and the other corresponding processors down the data processing flow. Record id is captured correctly on the GenerateTableFetch property state and its up to date as the record id from the  source (db). However, it will still miss some records when processing the files making the number of records on the destination out of sync with the source from the db. Am i missing something, Would scheduling times for fetching help and how can I do that? ... View more

Hi @Ayaz , @mburgess ! Please have a look at this spec as well! [ { "operation": "shift", "spec": { "*": { "BRANCH_CODE": "[&1].Fields.FLD0001", "CUST_NO": "[&1].Fields.FLD0002", "AC_DESC": "[&1].Fields.FLD0003", "CUST_AC_NO": "[&1].ExternalSystemIdentifier", "#1": "[&1].InstitutionId" } } } ]  Just FYI! ... View more

@mburgess @ljonnavi  Thank you! ... View more

Hi,    I am having exactly the same problem, I was wondering if it's possible to share the configuration did you use to get that result.    Thank you in advance! ... View more

@nkimani  when I change table name to "EMPLOYEE" it gives error 'stream has been closed' and when I give table name 'employee' it gives error 'none of the fields are matching with record map with employee table ' ... View more

Did you get a solution to this . I am also getting a communication error . My Nifi Instance and Mysql are on the same linux server .  ... View more

You cannot share states between processor, each processor has it's own state. ... View more

Is this (now) considered a NiFi "anti-pattern"? Do you have any idea how to do this using NiFi Record serialization services? I'm under the impression that creating thousands of content files is not the best practice by today's standards, but I'm not sure how to use InvokeHTTP on a full set of records without splitting it into many flowfiles. Any ideas? ... View more

For example I want to transform the zabbix payload from v4.0 to v4.4:   Zabbix Json Payload v4.0 (INPUT)   { "hosts": [ "Host B", "Zabbix Server" ], "groups": [ "Group X", "Group Y", "Group Z", "Zabbix servers" ], "tags": [ { "tag": "availability", "value": "" }, { "tag": "data center", "value": "Riga" } ], "name": "Either Zabbix agent is unreachable", "clock": 1519304285, "ns": 123456789, "eventid": 42, "value": 1 }     the JOLT transform:   [ { "operation": "shift", "spec": { "hosts": { "*": [ "hosts.[&].host", "hosts.[&].name" ] }, "*": "&" } } ]    The result ( Zabbix v4.4)   { "hosts" : [ { "host" : "Host B", "name" : "Host B" }, { "host" : "Zabbix Server", "name" : "Zabbix Server" } ], "groups" : [ "Group X", "Group Y", "Group Z", "Zabbix servers" ], "tags" : [ { "tag" : "availability", "value" : "" }, { "tag" : "data center", "value" : "Riga" } ], "name" : "Either Zabbix agent is unreachable", "clock" : 1519304285, "ns" : 123456789, "eventid" : 42, "value" : 1 }   ... View more