<?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 Re: The logical type TimeSpan is not supported in Delta format. Reason: Data Pipeline in Pipelines</title>
    <link>https://community.fabric.microsoft.com/t5/Pipelines/The-logical-type-TimeSpan-is-not-supported-in-Delta-format/m-p/4256895#M6053</link>
    <description>&lt;P&gt;Unfortunately, writing queries is not really an option at my company. Is there another way you can think of?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 24 Oct 2024 20:37:39 GMT</pubDate>
    <dc:creator>PWTRyanWhite</dc:creator>
    <dc:date>2024-10-24T20:37:39Z</dc:date>
    <item>
      <title>The logical type TimeSpan is not supported in Delta format. Reason: Data Pipeline</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/The-logical-type-TimeSpan-is-not-supported-in-Delta-format/m-p/4256587#M6047</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've seen this issue pop up for many users. Most responses consist of change the data type at the source, however, I cannot change the data type at the source. I have transformed the destination sink type to string but I keep getting the same issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any other thoughts other than just removing the fields from the data set?&lt;/P&gt;</description>
      <pubDate>Thu, 24 Oct 2024 15:48:59 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/The-logical-type-TimeSpan-is-not-supported-in-Delta-format/m-p/4256587#M6047</guid>
      <dc:creator>PWTRyanWhite</dc:creator>
      <dc:date>2024-10-24T15:48:59Z</dc:date>
    </item>
    <item>
      <title>Re: The logical type TimeSpan is not supported in Delta format. Reason: Data Pipeline</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/The-logical-type-TimeSpan-is-not-supported-in-Delta-format/m-p/4256725#M6049</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="660529" data-lia-user-login="PWTRyanWhite" class="lia-mention lia-mention-user"&gt;PWTRyanWhite&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are you able to query your source? You could write a query that uses casting in the select statement to change the column to a type that is supported.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Oct 2024 17:47:27 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/The-logical-type-TimeSpan-is-not-supported-in-Delta-format/m-p/4256725#M6049</guid>
      <dc:creator>FabianSchut</dc:creator>
      <dc:date>2024-10-24T17:47:27Z</dc:date>
    </item>
    <item>
      <title>Re: The logical type TimeSpan is not supported in Delta format. Reason: Data Pipeline</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/The-logical-type-TimeSpan-is-not-supported-in-Delta-format/m-p/4256895#M6053</link>
      <description>&lt;P&gt;Unfortunately, writing queries is not really an option at my company. Is there another way you can think of?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Oct 2024 20:37:39 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/The-logical-type-TimeSpan-is-not-supported-in-Delta-format/m-p/4256895#M6053</guid>
      <dc:creator>PWTRyanWhite</dc:creator>
      <dc:date>2024-10-24T20:37:39Z</dc:date>
    </item>
    <item>
      <title>Re: The logical type TimeSpan is not supported in Delta format. Reason: Data Pipeline</title>
      <link>https://community.fabric.microsoft.com/t5/Pipelines/The-logical-type-TimeSpan-is-not-supported-in-Delta-format/m-p/4266627#M6171</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="660529" data-lia-user-login="PWTRyanWhite" class="lia-mention lia-mention-user"&gt;PWTRyanWhite&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As &lt;STRONG&gt;FabianSchut&lt;/STRONG&gt; mentioned, the best way I can think of is to write some query steps as well:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Custom Conversion: Before writing to the Delta format, you can apply a custom conversion to convert the TimeSpan value to a supported format, such as a string representation of total milliseconds or seconds. This way, you can retain the TimeSpan information without losing data.&lt;/LI&gt;
&lt;LI&gt;Intermediate storage: Use an intermediate storage format that supports the TimeSpan type, such as Parquet and then convert to Delta format.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Best Regards,&lt;BR /&gt;Adamk Kong&lt;BR /&gt;&lt;BR /&gt;If this post &lt;EM&gt;&lt;STRONG&gt;helps&lt;/STRONG&gt;&lt;/EM&gt;, then please consider &lt;STRONG&gt;Accept it as the solution&lt;/STRONG&gt; to help the other members find it more quickly.&lt;/P&gt;</description>
      <pubDate>Fri, 01 Nov 2024 08:36:38 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Pipelines/The-logical-type-TimeSpan-is-not-supported-in-Delta-format/m-p/4266627#M6171</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-11-01T08:36:38Z</dc:date>
    </item>
  </channel>
</rss>

