Hi, What are you trying to do with those attributes? It doesnt make sense that you need to create an attribute for each year value ... View more

I'm not sure why your spec is producing this result, but to resolve it you can do the transformation on two shift operations: First to flatting json and move the subarray level to the root level and second to move the result and store it into an Array. Here is the spec I tried and it worked:   [ { "operation": "shift", "spec": { "MainArray": { "*": "ResultArray.&", "Subarray": { "*": "ResultArray.&" } } } }, { "operation": "shift", "spec": { "ResultArray": { "*": { "$": "ResultArray[#2][0]", "@": "ResultArray[#2][1]" } } } } ] ... View more

The ValidateXML processor will write the error to the attribute "validatexml.invalid.error". Check for that attribute when the flowfile is directed to the invalid relationship. Hope that helps ... View more

Hi Andre, Thanks again for taking the time and look into my access policy files. If you have noticed in the users.xml I have created an admin group with id "1966f436-0180-1000-ffff-ffffd1d17786" that the user "168b019c-0180-1000-ffff-fffffbf36c3a" is part of, this user group should have access to everything on the nifi canvas so Im assuming my user id implicitly will have access to everything as well, is that correct? even with that I went and give access to my user id explicitly to the target processor group with permission to view, modify and operate component, but still getting the 403 error! Keep in mind when I call the same API using nifi InovkeHttp providing the same access token it only works when I provide SSL Context Service that points to the same truststore & keystore files used to secure the nifi instance, could that be the problem in postman since I did not provide the SSL context there even though Im using https in the url? Im not sure how this can be configured in postman. Thanks for your help. ... View more

I sent you both the users and authorizations xml content in private message. Thanks! ... View more

Hi Andre,   I sent you the authorizers content in private message. thanks for your help ... View more

Hi Andre, Not sure what do you mean by "enabled Ranger for authorization"? Can you please elaborate? Also the user Im getting the access token for is the same user that can log in to nifi and have all kind of permissions added to view\modify any workflow. Not sure what else I could be missing. Thanks   ... View more