Question

A data engineer is ingesting IoT telemetry into a KQL database in an Eventhouse. The source files in a OneLake shortcut are JSON documents where each file contains a single JSON object spanning multiple lines (pretty-printed), not one object per line. An initial ingestion attempt using the default settings produced parsing errors and malformed rows. Which ingestion format setting should the engineer use so the files are parsed correctly?

Accepted Answer

Set the ingestion format to 'multijson' so the parser treats the entire file content as a whole JSON document rather than line-delimited records

Answer

Set the ingestion format to 'json', which expects one JSON object per line (newline-delimited)

Answer

Set the ingestion format to 'csv' and rely on an ingestion mapping to split the JSON fields

Answer

Set the ingestion format to 'raw' and parse the JSON later with an update policy