Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
My issue stems from the fact that an update policy cannot contain a join or lookup on a table with a streaming policy. I saw a post talking about a intermediary table . So I have tried to setup this work around, but continually get an error that the update policy cannot be implemented because the streaming policy on the b_stocks table.
Solved! Go to Solution.
@Hi @gstafflannel - Faced similar issue .
Can you separate streaming ingestion and enrichment which is recommended.
Update policy validation is based on the source lineage, not just the target table.
Joins are allowed only when the source table of the update policy is not streaming-derived. By separating ingestion and enrichment, the join happens on a non-streaming table.
Eg.
load_stocks
Streaming ingestion enabled
Raw data only (no joins / lookups)
b_stocks_enriched
Newly created table
No streaming ingestion ever enabled
Update policy sourced only from load_stocks (single-table query)
s_stocks
Update policy joins b_stocks_enriched with stock_sectors
Hope this helps
Proud to be a Super User! | |
Hi @gstafflannel ,
Thank you for reaching out to Microsoft Fabric Community.
Thank you @rajendraongole1 for the prompt response.
I wanted to check if you had the opportunity to review the information provided and resolve the issue..?Please let us know if you need any further assistance.We are happy to help.
Thank you.
Hi @gstafflannel,
Just wanted to follow up. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.
Thank you.
@Hi @gstafflannel - Faced similar issue .
Can you separate streaming ingestion and enrichment which is recommended.
Update policy validation is based on the source lineage, not just the target table.
Joins are allowed only when the source table of the update policy is not streaming-derived. By separating ingestion and enrichment, the join happens on a non-streaming table.
Eg.
load_stocks
Streaming ingestion enabled
Raw data only (no joins / lookups)
b_stocks_enriched
Newly created table
No streaming ingestion ever enabled
Update policy sourced only from load_stocks (single-table query)
s_stocks
Update policy joins b_stocks_enriched with stock_sectors
Hope this helps
Proud to be a Super User! | |
Experience the highlights from FabCon & SQLCon, available live and on-demand starting April 14th.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.