Version 2: This section describes how you can import JSON files into
The basic workflow task is described by way of example. In the example workflowtask, the JSON file must be imported into
|D s product|
This method of working with JSON is enabled by default.
NOTE: When this feature is enabled, all JSON imported datasets created under the legacy method must be recreated to behave like v2 datasets with respect to conversion and schema management. Features developed in the future may not retroactively be supported in the v1 legacy mode. You should convert to using the v2 method.
You can choose to continue using the legacy method of working with JSON.
Each row is a complete JSON record containing keys and values.
Tip: Nested JSON, such as
metricsabove, can be inserted as part of a record. It can then be unnested within the application.
Each key's value must have a comma after it, except for the final key value in any row.
NOTE: The end of a JSON record is the right curly bracket (}). Commas are not added to the end of each line in this format.
Import the JSON file.
- Any nested data must be unnested within columns. Each level in the JSON hierarchy must be un-nested in a separate step.
- When all of the JSON data is in tabular form, perform any
D s lang
- If you need to rebuild the loose JSON hierarchy, you must nest the lower levels of the JSON hierarchy back into their original form.
- If it is ok to write out flat JSON records, you can export without nesting the data again.
- Run the job, generating a JSON output.