Member since
10-03-2017
14
Posts
1
Kudos Received
0
Solutions
12-10-2021
12:31 AM
@krishna123 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
09-26-2020
02:37 AM
spark-xml package is a good option too. With all options you are limited to only process simple XMLs which can be interpreted as dataset with rows and columns. However, if we make it a little complex, those options won’t be useful.
... View more
02-01-2020
05:40 AM
I have uploaded a NiFi example template on https://github.com/maxbback/nifi-xml
... View more
03-11-2018
12:43 PM
Hi Kylo is providing the functionality you are looking for They have a concept together with nifi which is called reusable flow This flow can be connected to any feed templates and in the end all feeds hook into the same reusable flow in nifi So in short you create a flow in nifi with input port, create a template of this flow the reusable flow, export it and inport the file as a reusable flow in kylo. Create your feed template flows in nifi and create template of them, import the template from nifi in kylo and connect the output port of your template to the input port of the reusable flow. Create a feed in kylo from your template. Kilo will then generate a feed based on your feed template in nifi and connect this to the reusable flow. You can now modify your reusable flow and create a new template in nifi with the same name as the previous version of the reusable flow, export it to a file and import it to kylo and all your feeds are now connected to the new version of your reusable flow. If you do not want to use Kylo there is an alternative you create a group called reusable flow In this group you create a group called reusable flow v1 You connect your feeds to the input port on the reusable flow group And inside of the reusable flow you connect it to the v1 groups input port Now you want to make a new version of your reusable flow You make a copy of the group v1 to v2 Make the changes you want to do inside of v2, when you are satisfied you disconnect v1 and connect v2 instead. In this way it is very easy to switch to a new version without having to change any of your feeds. Below is link to youtube that describe the kylo reusable flow, but if you are only in nifi I recommend the groups in groups to maintain different versions as you then can easily switch back and forward without impacting all your feeds https://www.youtube.com/watch?v=Vj641MRJCd8
... View more
05-15-2018
04:37 PM
Since this isn't related to the original question, please ask this as its own standalone question and I'd be happy to answer it. (The short answer is you might be able to use UpdateAttribute to change the 4 to the right column number for Table B if you can figure out whether a flow file is for Table A or B)
... View more
07-01-2018
01:59 PM
Hi XML tree is a complex as they are hierarchical and you most likely want a flat structure for easier access of the data. I just wrapped up the second article of this yesterday, and the code for this is available at GitHub link included in the article. http://max.bback.se/index.php/2018/06/30/xml-to-tables-csv-with-nifi-and-groovy-part-2-of-2/ The article describe the problem and is providing an implementation for the conversion from XML to CSV by flattening out the XML files, my example XML is flattened out into 4 tables, all depends on how many branches you have that is of the type 1 to many. /Max
... View more