A municipal water-taxi kiosk emits nested JSON boarding events that operations staff still open in a text editor. Next quarter the same objects will be scanned as flat columns for a no-show model. When should the team keep JSON, and when should they convert?
Select an answer to reveal the explanation.
Short Explanation
Think of nested boarding JSON that staff still open in a text editor, then later flat column scans for a no-show model. Keep JSON for the nested ingest. Convert to columnar when the jobs start picking fields.
Full Explanation
JSON matches nested, document-style ingest. A columnar format matches later analytic scans of selected fields. Deleting JSON on day one drops the editor path too early. Nested JSON is not already a column layout, and RecordIO is not an editor format.