DSXchange

Hi all. Hope all is well. Tomorrow is my last day at IBM. I will be taking a management role at MANTA (www.getmanta.com ), a player in the metadata integration and data lineage space. Thanks for all the experiences with XML, JSON, Server Jobs, IGC, data lineage, Glossary stuff, and so much more........

As Craig notes, more detail is needed...you need to map the "lists" from your imported JSON (in the Library Manager you can review it, or at the "root" part of the JSON composer).....this is a very difficult stage to learn initially..... browse also any/all of the xml compose or ...

Hi. I don't have any experience with Kudo, but in past threads here and elsewhere over the years, I've heard many people talk about loading to their hive and hive related tables using direct writes to the hdfs files that they are abstracting....much faster.....usually using the File Connector. Ernie

Try this...it might provide you with some options, if the change in payload is impacting the default output link parsing.... ....by default, the stage takes the details for parsing the output link from the WSDL itself...but at times, the WSDL might be wrong, incomplete, edited, or for some other des...

Congratulations! That's wonderful. Happy for you, and yes...come visit!

Ernie

Repetition Element is merely an "indicator".....for an element in the "deepest node that you care about" and that "reliably" always exists in the document. That element controls whether the Stage thinks that the node is "missing" or "present", and de...

A couple of things... 1. the first scenario, name telephone....they can easily be parsed and retrieved all on one single output link, exactly as you have it. You only need a single link for all directly nested nodes. So in your case, it doesn't sound like you have 24 complete "paths" thru ...

Good one!

What is your ultimate goal? Are you writing xml that is coming from many different relational tables? ...or parsing/reading incoming XML and putting together a result? Also...spend time reviewing an actual document itself...if everything is entirely unbounded, it often means that "it was the si...

Great job! Thanks for sharing.

I can imagine some possibilities, but there is too much room for interpretation. Can you describe the issue in a bit more detail? ...perhaps outline some of the resulting xml you are seeing and what you "want" to see?

Thanks.

Ernie

The biggest key to parsing structures in the hierarchical stage is in the very first thing you need to do when you arrive at the mapping page.....before you do ANYTHING else, first map "the lowest level list that you care about" to the list of the output link..... Blue list icon to blue li...

Thank you for the kind words. Glad these resources have been helpful. I havent done cdata stuff in awhile, but recall researching this in depth and concluding that it cant be done with the hierarchical stage.....needing still the xmlOutput Stage....which, for subtle reasons like this, is still fully...

There are MANY nuances for the hierarchical stage. Critical best practice one is to always map your bottom list first, to your output link, before you do ANYTHING else. Second....one repeating path per output link. Third....parse and get out......do joins and aggregations outside of the stage. There...

It has been awhile since I tried it but I seem to recall there being an issue where it appends the schema location with the fully qualified Engine subdirectory.

Ernie