Forum Discussion
Changing string storage for DirectLake over OneLake
You are welcome jaryszek
By “reshape the data in OneLake,” I mean cleaning or restructuring your source tables before DirectLake reads them:Cut down very long or unique text columns (hash them or move them to a lookup).
Trim or split oversized fields.
Pre‑aggregate or filter data so fewer distinct values are loaded.
In short you need to adjust the Lakehouse tables so DirectLake doesn’t choke on huge text fields.
Did it work? 👍 A kudos would be appreciated
🟨 Mark it as a solution to help spread knowledge 💡
Thank you very much,
"to reshape the data in OneLake " what does you mean by that?
Best,
Jacek
You are welcome jaryszek
By “reshape the data in OneLake,” I mean cleaning or restructuring your source tables before DirectLake reads them:
Cut down very long or unique text columns (hash them or move them to a lookup).
Trim or split oversized fields.
Pre‑aggregate or filter data so fewer distinct values are loaded.
In short you need to adjust the Lakehouse tables so DirectLake doesn’t choke on huge text fields.
Did it work? 👍 A kudos would be appreciated
🟨 Mark it as a solution to help spread knowledge 💡
thank you very much