Member since
11-16-2015
892
Posts
649
Kudos Received
245
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
5140 | 02-22-2024 12:38 PM | |
1335 | 02-02-2023 07:07 AM | |
2999 | 12-07-2021 09:19 AM | |
4152 | 03-20-2020 12:34 PM | |
13928 | 01-27-2020 07:57 AM |
10-04-2024
04:54 AM
@mjmoore
Have you been able to resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.
... View more
09-28-2024
07:03 PM
1 Kudo
Thanks to the second OP for identifying the root cause in the NiFi Jira. For people researching this today, the cause was the implicit/default Namespace specified in the root node (the 'xmlns' referenced in that element but without a suffix). In the case of the second poster, their XML started with: <data xmlns="http://www.media-saturn.com/msx" xmlns: ... The `/data/item//uniqueID` he was searching for belongs to, more accurately, the "http://www.media-saturn.com/msx" namespace, meaning that - he was supposed to - specify that namespace as part of his XPath expression. The reason that searching for the pathless "//@uniqueType" worked, was because that search searches all namespaces for that XPath expression! I'm using NiFi 2.0.0 M4 today and I'm pleased to report that it appears to support the XPath 3.0/3.1 notation where the Namespace can be specified inline with the query. It's not particularly elegant - but it works. You prefix the Namespace with the capital Letter 'Q' and wrap it in curly brackets; namely: Q{http://www.media-saturn.com/msx}<single-level selector> To implement his expression, "/data/item//uniqueID[UniqueType='ProdID']/text()" which currently returns an Empty String set for Key 'ProdID4', you would use: /Q{http://www.media-saturn.com/msx}data/Q{http://www.media-saturn.com/msx}item//uniqueID[UniqueType='ProdID']/text() I have a suspicion that the second Namespace reference (to 'item' in this case) is not required, since once you've selected/are navigating down the 'data' path of the correct Namespace, you're not likely to jump to another Namespace? My research indicates that Attributes do not seem to accept Namespace referencing - but again, once you've successfully selected your path I suspect it becomes a moot point. Aside, [1] it would be nice if the NiFi documentation specified the version of the XPath implemented within the Processor. [2] Even better if there were a drop down within the Processor that allowed a developer to select the version of XPath expression desired.
... View more
08-13-2024
09:28 PM
@mburgess -- I am reading from Oracle table, not sure about the incoming flowfile
... View more
07-31-2024
03:23 AM
1 Kudo
@Adyant001, Welcome to the Cloudera Community. 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
04-26-2024
02:01 AM
1 Kudo
Hi @mburgess , tried increasing the Entity time tracking window to 8 hours (the time difference is 7hrs here from PDT to UTC), but still could see the same files getting listed, not the latest ones from source server as expected. Attached the Nifi ListSFTP configuration i'm using.
... View more
03-20-2024
08:17 AM
Hi there @mburgess thank you for your reply. Let play around with your solution and see if i can get it working and write the output to a flowfile 🤓
... View more
03-13-2024
05:57 AM
1 Kudo
Hi Diana, good idea. I'll create a new thread. Thank you.
... View more
02-23-2024
11:51 AM
1 Kudo
https://issues.apache.org/jira/browse/NIFI-12839
... View more
02-15-2024
06:05 AM
How do you iterate the getAttributes() in Java? It won't work using just that method
... View more