<?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 Guidance for creating DLT pipeline with raw json call logs in Administration &amp; Architecture</title>
    <link>https://community.databricks.com/t5/administration-architecture/guidance-for-creating-dlt-pipeline-with-raw-json-call-logs/m-p/59824#M852</link>
    <description>&lt;P&gt;Hi I am looking for some support on how to handle the following situation.&amp;nbsp; I have a call center that generates call log files in json format that are sent to an s3 bucket.&amp;nbsp; Some of the raw json files contain more than one call log object and they are not in correct json format.&amp;nbsp; I.e. they are one large json file with objects right after each other and may contain up to 8 of these jsons.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I want to&amp;nbsp;create a delta live data processing pipeline that will&lt;BR /&gt;1. ingest new files twice daily&lt;BR /&gt;2. separate the individual json objects into one file for each object&lt;BR /&gt;3. create a table with the json objects&lt;BR /&gt;4. clean the data to get rid of incomplete data&lt;BR /&gt;5. add some data columns such as callers who hung up and immediately called back&lt;BR /&gt;6. produce aggregated statistics about the calls&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;some of the questions I have are:&lt;BR /&gt;1. should I ingest the raw json files into a bronze table without separating them out, or separate them before adding them to the bronze level&lt;BR /&gt;2.&amp;nbsp; My file live an an s3 bucket that is mounted to my db workspace, does this mean they are already in the "bronze" level, or do i need to copy them from the mounted directory into the DLT pipeline?&lt;/P&gt;</description>
    <pubDate>Fri, 09 Feb 2024 18:21:33 GMT</pubDate>
    <dc:creator>chrisf_sts</dc:creator>
    <dc:date>2024-02-09T18:21:33Z</dc:date>
    <item>
      <title>Guidance for creating DLT pipeline with raw json call logs</title>
      <link>https://community.databricks.com/t5/administration-architecture/guidance-for-creating-dlt-pipeline-with-raw-json-call-logs/m-p/59824#M852</link>
      <description>&lt;P&gt;Hi I am looking for some support on how to handle the following situation.&amp;nbsp; I have a call center that generates call log files in json format that are sent to an s3 bucket.&amp;nbsp; Some of the raw json files contain more than one call log object and they are not in correct json format.&amp;nbsp; I.e. they are one large json file with objects right after each other and may contain up to 8 of these jsons.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I want to&amp;nbsp;create a delta live data processing pipeline that will&lt;BR /&gt;1. ingest new files twice daily&lt;BR /&gt;2. separate the individual json objects into one file for each object&lt;BR /&gt;3. create a table with the json objects&lt;BR /&gt;4. clean the data to get rid of incomplete data&lt;BR /&gt;5. add some data columns such as callers who hung up and immediately called back&lt;BR /&gt;6. produce aggregated statistics about the calls&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;some of the questions I have are:&lt;BR /&gt;1. should I ingest the raw json files into a bronze table without separating them out, or separate them before adding them to the bronze level&lt;BR /&gt;2.&amp;nbsp; My file live an an s3 bucket that is mounted to my db workspace, does this mean they are already in the "bronze" level, or do i need to copy them from the mounted directory into the DLT pipeline?&lt;/P&gt;</description>
      <pubDate>Fri, 09 Feb 2024 18:21:33 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/guidance-for-creating-dlt-pipeline-with-raw-json-call-logs/m-p/59824#M852</guid>
      <dc:creator>chrisf_sts</dc:creator>
      <dc:date>2024-02-09T18:21:33Z</dc:date>
    </item>
  </channel>
</rss>

