Changing Ingestions from JSON

Hi MoFabricIoT​ 

Thanks for testing that. The field not returning even after you changed the JSON back to y is the key clue — the blocking state isn't in your JSON.

Start with one test: check the eventstream's data preview / Live view. If y appears correctly there but never reaches the KQL table, the issue is at the ingestion stage. If it's already missing in the eventstream, the issue is upstream in the inferred schema review it, republish, and send a new event.

If the value reaches the eventstream but not the table, try these in order:

Clear the streaming schema cache. This best fits your symptom. Eventhouse nodes cache the schema of databases that get data through streaming ingestion, and when the cache falls out of sync you can see "incomplete and distorted data in the table". It refreshes automatically, but that "can take several minutes" force it with:

.clear table <TableName> cache streamingingestion schema 

Check for a database-scoped mapping. Your table-scoped query wouldn't have shown one — .show works for "a database or table":

.show database <DatabaseName> ingestion mappings

Review the destination's captured configuration. Direct ingestion creates a Data connection and captures the column setup at that moment. In Live view, select Configure on the Eventhouse destination node, then check Edit columns and the Table_mapping dropdown.

I wouldn't call this a bug until the schema cache and the eventstream schema are ruled out. If all three come back clean and rows still don't land, raise a support ticket via Help (?) with your data connection name, table name and a UTC time window.

Thanks,
Srikanth Cheri