@nverwer wrote: Instead of using local-name, you can also do this: //*:textNOTAM This has a wildcard for the namespace prefix, and the element name in the place where you would expect it. This tends to be more readable for longer XPaths like //*:feed//*:entry//*:title This info was hard to find. @nverwer thanks. Saved my day! ... View more

Hi @M-Boufnichel as this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. ... View more

This can be done by jolt like this: [ { "operation": "modify-overwrite-beta", "spec": { "issued_year": "=substring(@(1,issued),0,4)", "issued_month": "=substring(@(1,issued),5,7)", "issued_day": "=substring(@(1,issued),8,10)", "issued_hour": "=substring(@(1,issued),11,13)", "issued_minute": "=substring(@(1,issued),14,16)", "issued_second": "=substring(@(1,issued),17,19)" } }, { "operation": "shift", "spec": { "issued_year": "issued_year", "issued_month": "issued_month", "issued_day": "issued_day", "issued_hour": "issued_hour", "issued_minute": "issued_minute", "issued_second": "issued_second" } } ] ... View more

 Hi   for this flow  can you share what was teh content of the flow file. and what was the configuration in put mongo.    I am facing the same issues.    Thanks Rupesh ... View more

HI @Shu. Could you please explain what sysdate, current_date, etc would do for me with the spark job? I dont fully understand how to use them and the benefits that this technique would offer. ... View more

I've finally worked through this challenge. It was a bit of a struggle for me, since there is inadequate documentation on some of these lower-level developer details. However I did take the time to capture what I learned along the way. Currently I placed this learning here. If I capture more detail on this process, i will place it in the same NiFi issue. ... View more

I fiddled with the XML and I found that the issue is having data in form of XML attributes. For example if the longitude and latitude data is in this format, you get the desired output. Seems like there is some issue in the XMLReader. I upvoted your JIRA issue. Lets wait and see. Thanks for your response. ... View more

I think this may be a bug in the NIFI JoltTransformRecord processor. What is the best way to register this bug? ... View more

Thank you @Matt Burgess for the key operation that i was missing. Keep in mind, I still need the shift operation since I am reducing a more complex JSON as part of the shift So the entire spec contains two operations as follows.. [ { "operation": "shift", "spec": { "textNOTAM": { "NOTAM": { "id": "&0", "number": "&0", "year": "&0", "type": "&0", "issued": "&0", "affectedFIR": "&0", "minimumFL": "&0", "maximumFL": "&0", "radius": "&0", "location": "&0", "effectiveStart": "&0", "effectiveEnd": "&0", "schedule": "&0", "text": "&0" } } } }, { "operation": "modify-overwrite-beta", "spec": { "effectiveStart": "=toString", "effectiveEnd": "=toString" } } ] ... View more

@David Sargard, "@" copies whatever is present at the current level, and copies it to "&2.&" Here &2 means go up two levels and grab the key, and & means go up one level and grab the key. i.e., &2 will return textNOTAM and & will return NOTAM, so &2.& will place whatever value you get at the following jsonPath: textNOTAM.NOTAM ... View more