Forum Discussion
Sudden Format change from JSON to TXT in Datastream
Since Databricks is still ingesting the data correctly, the issue is likely within Fabric’s data ingestion or transformation process.
First, verify your Fabric data stream settings, especially the ingestion method and format configurations, as the initial multi-JSON format might have been altered due to a setting change. Check if the schema of the EventHub data has changed, if metadata or system properties are missing, Fabric might be defaulting to a TXT format instead of JSON.
Ensure that system properties are still selected in the Fabric data ingestion settings and try reconfiguring the ingestion to force their inclusion. Also, check if any recent Microsoft Fabric updates may have impacted how data streams handle JSON formats.
If nothing works, try recreating the data stream from scratch and explicitly setting the format to multi-JSON during configuration. Since the issue persists within Fabric but not in Databricks, it strongly suggests an internal setting or schema mismatch rather than a problem with EventHub.
Resolver ISince Databricks is still ingesting the data correctly, the issue is likely within Fabric’s data ingestion or transformation process.
First, verify your Fabric data stream settings, especially the ingestion method and format configurations, as the initial multi-JSON format might have been altered due to a setting change. Check if the schema of the EventHub data has changed, if metadata or system properties are missing, Fabric might be defaulting to a TXT format instead of JSON.
Ensure that system properties are still selected in the Fabric data ingestion settings and try reconfiguring the ingestion to force their inclusion. Also, check if any recent Microsoft Fabric updates may have impacted how data streams handle JSON formats.
If nothing works, try recreating the data stream from scratch and explicitly setting the format to multi-JSON during configuration. Since the issue persists within Fabric but not in Databricks, it strongly suggests an internal setting or schema mismatch rather than a problem with EventHub.