Hi @calonsca! Please have a look at this spec as well! [ { "operation": "shift", "spec": { "@": "data", "ID": "&", "#${date}": "date", "#${dataset:toLower()}": "dataset" } } ] ... View more

Hi @DataD, Please find the below spec: [ { "operation": "shift", "spec": { "rows": { "*": { "row": { "*": { "@": "[&3].@(3,header[&1])" } } } } } } ] This will give the output as: [ { "header1" : "row1", "header2" : "row2", "header3" : "row3" }, { "header1" : "row4", "header2" : "row5", "header3" : "row6" } ] I didn't convert it to  { "header1" : "row1", "header2" : "row2", "header3" : "row3", "header1" : "row4", "header2" : "row5", "header3" : "row6" } because that is not a valid json as header1,2 and 3 are repeated keys in the same level of the json. ... View more

Hi @Biswa, Please look at the below spec: [ { "operation": "shift", "spec": { "*": { "urlTypeName": { "Spring URL": { "@(2,examUrl)": "ExamDashBoardURL[]" } } } } } ] Output will be: { "ExamDashBoardURL" : [ "https://exam.test.com/page/1473161074" ] } Tell me if this is ok. ... 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

Hi @Sru111, Setting the FetchSFTP processor to run on primary node is fine. But, if there are multiple files that you need to fetch from SFTP using the same processor, fetching of second file will happen only after you fetch first one (Similarly for the rest). But, you can fetch them simultaneously. So, using all the 3 nodes is preferred for FetchSFTP processor. May I know which version of nifi you are using? I believe, load balance strategy was introduced in 1.11.0 (not sure) but, started working correctly in 1.11.4 version.   Regarding PutHDFS, I don't have a clue about it! Sorry! ... View more

Hi @Sru111 , Consider the MergeContent processor in the picture as your MergeContent processor. Configure the queue(here, 'success') that acts as the upstream queue for your MergeContent processor. Select the load balance strategy as Single node, then you will get all the files as input to only one of the nodes. (Optional) You can configure the donwstream queue of MergeContent processor to have the load balance strategy as Round Robin, so that the files are distributed among all the nodes in the cluster. ... View more

Hi @wcbdata  Can you explain the usage of '#' in the spec you used above: {     "operation": "shift",     "spec": {       "tmp": {         "*": {           "0": {             "*,*,*,*": {               "@(4,runid)": "particles.[#4].runid",               "@(4,ts)": "particles.[#4].ts",               "$(0,1)": "particles.[#4].Xloc",               "$(0,2)": "particles.[#4].Yloc",               "$(0,3)": "particles.[#4].Xdim",               "$(0,4)": "particles.[#4].Ydim"             }           }         }       },       "*": "&"   }  }    ... View more