<?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 Lakehouse Table Schema setup after Eventstream in Eventstream</title>
    <link>https://community.fabric.microsoft.com/t5/Eventstream/Lakehouse-Table-Schema-setup-after-Eventstream/m-p/4263866#M250</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I add a new table as a destination in eventstream, I get an error saying 'table not found'.&amp;nbsp;&lt;/P&gt;&lt;P&gt;So do I need to create a table before the eventstream is set up?&amp;nbsp;&lt;/P&gt;&lt;P&gt;And does it then have to have the correct schema before events are pushed to the stream?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best,&lt;/P&gt;&lt;P&gt;BW&lt;/P&gt;</description>
    <pubDate>Wed, 30 Oct 2024 12:38:06 GMT</pubDate>
    <dc:creator>bw_chec</dc:creator>
    <dc:date>2024-10-30T12:38:06Z</dc:date>
    <item>
      <title>Lakehouse Table Schema setup after Eventstream</title>
      <link>https://community.fabric.microsoft.com/t5/Eventstream/Lakehouse-Table-Schema-setup-after-Eventstream/m-p/4263866#M250</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I add a new table as a destination in eventstream, I get an error saying 'table not found'.&amp;nbsp;&lt;/P&gt;&lt;P&gt;So do I need to create a table before the eventstream is set up?&amp;nbsp;&lt;/P&gt;&lt;P&gt;And does it then have to have the correct schema before events are pushed to the stream?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best,&lt;/P&gt;&lt;P&gt;BW&lt;/P&gt;</description>
      <pubDate>Wed, 30 Oct 2024 12:38:06 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Eventstream/Lakehouse-Table-Schema-setup-after-Eventstream/m-p/4263866#M250</guid>
      <dc:creator>bw_chec</dc:creator>
      <dc:date>2024-10-30T12:38:06Z</dc:date>
    </item>
    <item>
      <title>Re: Lakehouse Table Schema setup after Eventstream</title>
      <link>https://community.fabric.microsoft.com/t5/Eventstream/Lakehouse-Table-Schema-setup-after-Eventstream/m-p/4264679#M252</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="777286" data-lia-user-login="bw_chec" class="lia-mention lia-mention-user"&gt;bw_chec&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;do I need to create a table before the eventstream is set up?&lt;/LI-CODE&gt;
&lt;P&gt;No. You can create it directly when configuring the destination:&lt;/P&gt;
&lt;P&gt;&lt;img /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;does it then have to have the correct schema before events are pushed to the stream?&lt;/LI-CODE&gt;
&lt;P&gt;It would be best if this is the case, please refer to the reply in the following link:&lt;BR /&gt;&lt;A href="https://community.fabric.microsoft.com/t5/Eventstream/Handling-schema-changes-and-multiple-schemas-in-Eventstream/td-p/4051188" target="_blank"&gt;Solved: Handling schema changes and multiple schemas in Ev... - Microsoft Fabric Community&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;Dino Tao&lt;BR /&gt;If this post &lt;EM&gt;&lt;STRONG&gt;helps&lt;/STRONG&gt;&lt;/EM&gt;, then please consider &lt;EM&gt;&lt;STRONG&gt;Accept it as the solution&lt;/STRONG&gt;&lt;/EM&gt; to help the other members find it more quickly.&lt;/P&gt;</description>
      <pubDate>Thu, 31 Oct 2024 01:42:23 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Eventstream/Lakehouse-Table-Schema-setup-after-Eventstream/m-p/4264679#M252</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-10-31T01:42:23Z</dc:date>
    </item>
    <item>
      <title>Re: Lakehouse Table Schema setup after Eventstream</title>
      <link>https://community.fabric.microsoft.com/t5/Eventstream/Lakehouse-Table-Schema-setup-after-Eventstream/m-p/4367116#M325</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="777286" data-lia-user-login="bw_chec" class="lia-mention lia-mention-user"&gt;bw_chec&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Please check this :&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;1. Do You Need to Create the Table Beforehand?&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;Yes, you need to either create the table beforehand or allow the Eventstream to create it dynamically. If you select an existing table as the destination, it must already exist in your Lakehouse. Alternatively, you can configure the Eventstream to create a new Delta table when setting up the destination.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;2. Does the Table Need the Correct Schema?&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;Schema Enforcement: Microsoft Fabric enforces schema compatibility when writing data into a Lakehouse destination table. If you are using an existing table, its schema must match the incoming data from the Eventstream. Any discrepancies, such as missing or extra columns, may result in errors or data being written with NULL values for missing fields.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Dynamic Schema Creation: When creating a new Delta table via the Eventstream configuration, the schema is inferred from the first record of incoming data. All subsequent records are projected onto this schema.&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jan 2025 11:19:20 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Eventstream/Lakehouse-Table-Schema-setup-after-Eventstream/m-p/4367116#M325</guid>
      <dc:creator>nilendraFabric</dc:creator>
      <dc:date>2025-01-16T11:19:20Z</dc:date>
    </item>
  </channel>
</rss>

