Hi @praneet , Can you add Authorization inside "Attributes to Send" property and tell me if you are still getting the error? ... View more

Hi @Manoj90 , Please terminate original relation from GetHTMLElement. The reason you are getting so many flowFiles is as follows: On the first run, GetHTMLElement processor is returning 10 flowFiles to the "success" relation. As the operation was successful, the input flowFile(10.79 KB) will be routed to original relation as well. Then, you have the same file which was input for GetHTMLElement processor. Again, it starts processing and sends 10 flowFiles to success relation and the original(input) flowFile to original relation. This loop will continue infinitely till you get memory issue. ... View more

Hi @kquintero, Can you put the attribute into flowFile content and see if the spaces are removed in the content as well? From what I know, attributes won't show extra spaces, but, the spaces are still present. Even when you hover over those values, you can still see the empty spaces. ... View more

Hi @vineet_harkut , To check if the required parameters are valid in MongoDB processor, what I would do is Suppose, there is a query like {"key":"someValue","name":"someOtherValue"}. And "someValue" and "someOtherValue" are values inside the attributes of the incoming flowFile with attribute-names "key" and "name" respectively. Hence, the resulting query in the GetMongo processor will be {"key":"${key}","name":"${name}"}. Before using the GetMongo processor, I would use RouteOnAttribute processor to check if the input to the query is a valid one. If the input is correct, I will make a query to the GetMongo processor. If the document for the query is not found, the GetMongo processor will return empty document (empty string) as content in the flowfile only when Send Empty Result is set to true inside the GetMongo processor. Later, when I use EvaluateJsonPath processor, the flowfile will be routed to "failure" when the flowfile is empty, as empty string is not a valid JSON or to "matched" if the match for the given jsonPath is found. This will put the same content inside the flowfile as $ corresponds to entire JSON object that we are getting from the input flowfIle. Now, you can add the remaining logic. ... 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

Hi @praneet ! Look at the spec I used Input used: { "Подписка":"awdl" } Spec: [ { "operation": "shift", "spec": { "Подписка":"Подпиа" } } ] Output got: {"Подпиа":"awdl"} I was able to perform jolt without any problems in nifi-1.11.4 Tell me if you are still facing the issues. ... View more

Hi @Kilynn ! Firstly, I tried to use regex to replace "}       {" (variable space) with "},{". Then, I tried adding square brackets at the beginning and the end ( "[" and "]" ). Then, I got a valid Json. ReplaceText config: Groovy code: import org.apache.commons.io.IOUtils import java.nio.charset.StandardCharsets flowFile = session.get() if (!flowFile) return try { def input = ''; session.read(flowFile, {inputStream -> input = IOUtils.toString(inputStream, StandardCharsets.UTF_8) } as InputStreamCallback); flowFile = session.putAttribute(flowFile,'Content-Type','application/json'); flowFile = session.putAttribute(flowFile,'mime.type','application/json'); flowFile = session.write(flowFile, { outputStream -> outputStream.write(('['+input+']').toString().getBytes(StandardCharsets.UTF_8)) }as OutputStreamCallback); session.transfer(flowFile, REL_SUCCESS); } catch (e) { log.error('Error Occured,{}', e) session.transfer(flowFile, REL_FAILURE); } ... View more