<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic JSON, TDM and MongoDB input and output w/o loosing nested hierarchies in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/JSON-TDM-and-MongoDB-input-and-output-w-o-loosing-nested/m-p/2229418#M20366</link>
    <description>I would like to be able to process MongoDB (JSON) hierarchies in and out out Talend Integration &amp;amp; Mapping perspectives without loosing nested hierarchies.
&lt;BR /&gt;The mapping perspective works fine with JSON but how do I get nested loops in and out of TDM in a integration Job.
&lt;BR /&gt;The problem is not so much moving things at the top of the hierarchy at a field level but more how JSON is defined as both input and output in the DI metadata. I don't think nested looping is possible.
&lt;BR /&gt;This may be possible today and I might be miss-using components or we have to consider how effective we will be in the MongoDB area without these capabilities.&amp;nbsp;
&lt;BR /&gt;It would be nice to treat JSON hierarchies more like we treat XML. Leave them intact and maybe even have a TJSONMAP component and then move at the field level leaving all hierarchies intact.</description>
    <pubDate>Tue, 24 Feb 2015 18:10:28 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2015-02-24T18:10:28Z</dc:date>
    <item>
      <title>JSON, TDM and MongoDB input and output w/o loosing nested hierarchies</title>
      <link>https://community.qlik.com/t5/Talend-Studio/JSON-TDM-and-MongoDB-input-and-output-w-o-loosing-nested/m-p/2229418#M20366</link>
      <description>I would like to be able to process MongoDB (JSON) hierarchies in and out out Talend Integration &amp;amp; Mapping perspectives without loosing nested hierarchies.
&lt;BR /&gt;The mapping perspective works fine with JSON but how do I get nested loops in and out of TDM in a integration Job.
&lt;BR /&gt;The problem is not so much moving things at the top of the hierarchy at a field level but more how JSON is defined as both input and output in the DI metadata. I don't think nested looping is possible.
&lt;BR /&gt;This may be possible today and I might be miss-using components or we have to consider how effective we will be in the MongoDB area without these capabilities.&amp;nbsp;
&lt;BR /&gt;It would be nice to treat JSON hierarchies more like we treat XML. Leave them intact and maybe even have a TJSONMAP component and then move at the field level leaving all hierarchies intact.</description>
      <pubDate>Tue, 24 Feb 2015 18:10:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/JSON-TDM-and-MongoDB-input-and-output-w-o-loosing-nested/m-p/2229418#M20366</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2015-02-24T18:10:28Z</dc:date>
    </item>
    <item>
      <title>Re: JSON, TDM and MongoDB input and output w/o loosing nested hierarchies</title>
      <link>https://community.qlik.com/t5/Talend-Studio/JSON-TDM-and-MongoDB-input-and-output-w-o-loosing-nested/m-p/2229419#M20367</link>
      <description>Hi&amp;nbsp;
&lt;BR /&gt;Can tExtractJsonFields fit the need? which&amp;nbsp;can be used to extract data from a json string after you read the nested loop as a node.&amp;nbsp;
&lt;BR /&gt;Best regards
&lt;BR /&gt;Shong</description>
      <pubDate>Fri, 27 Mar 2015 00:58:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/JSON-TDM-and-MongoDB-input-and-output-w-o-loosing-nested/m-p/2229419#M20367</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2015-03-27T00:58:39Z</dc:date>
    </item>
  </channel>
</rss>

