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.
- Recommended limit of 1 GB in source file size. Since conversion happens within the
, this limit may vary depending on the memory of the
D s node
D s node
Each JSON record must be less than 20 MB in size.
- Filename extensions must be
- Conversion of compressed JSON files is not supported. Compressed JSON files can be imported using the previous method. See Working with JSON v1.
For best results, all keys and values should be quoted and imported as strings.
NOTE: Escape characters that make JSON invalid can cause your JSON file to fail to import.
You can escape quote values to treat them as literals in your strings using the backslash character. For example:
- When the values are imported into the Transformer page, the
re-infers the data type for each column.
D s webapp
Through the Import Data page, navigate and select your JSON file for import.
NOTE: File formats are detected based on the file extension. Please verify that your file extension is
.JSON, which ensures that it is passed through the conversion service.
The file is passed through the conversion process, which reviews the JSON file and stores it on the base storage layer in a format that can be easily ingested as in row-per-record format. This process happens within the Import Data page. You can track progress on the right side of the screen.
After the file has been converted, click the Preview icon on the right side of the screen. In the Preview, you can review the first few rows of the imported file.
If some rows are missing from the preview, then you may have a syntax error in the first row after the last well-structured row. You should try to fix this in source and re-import.
If all of the rows are problematic, your data is likely malformed.
Complete the rest of the import process. For more information, see Import Data Page .Add
- In Flow View, add the JSON-based imported dataset to a your flow and create a recipe for it. For more information, see Flow View Page.
- Select the recipe, and click Edit Recipe....
M/07/1'3" [23lbs > 13lbs = 10lbs] Still a bit to go, but my owner no longer refers to me as his chunky boy!
M/29/5'11" [605 pounds > 375 pounds = 230 pounds lost] (14 months) Still considered super morbidly obese but I've made some good progress.
F/28/5’7” [233lbs to 130lbs] Got tired of being obese and took control of my life!
M/22/5'11" [99lbs > 150lbs = 51lbs] Anorexia my recovery
|D s also|