Based on the customer feedback in the latest version of Advanced ETL Processor we have introduced support for JSON
What is JSON
Benefits of using JSON
JSON is much more efficient than XML. It requires less network traffic processing power and memory to work with
- JSON only has three simple types – strings, numbers and Booleans – and two complex types – arrays and objects.
- A string is a sequence of zero or more characters wrapped in quotes with backslash escapement, the same notation used in most programming languages.
- A number can be represented as an integer, real, or floating-point. JSON does not support octal or hex. It does not have values for NaN or Infinity. Numbers are not quoted.
- A JSON object is an unordered collection of key/value pairs. The keys are strings and the values are any of the JSON types. A colon separates the keys from the values, and a comma separates the pairs. The whole thing is wrapped in curly braces.
- The JSON array is an ordered collection of values separated by commas and enclosed in square brackets.
- The character encoding of JSON text is always Unicode. UTF-8 is the only encoding that makes sense on the wire, but UTF-16 and UTF-32 are also permitted.
- JSON has no version number. No revisions to the JSON grammar are anticipated.
- JSON's syntax is significantly simpler than XML, so parsing is more efficient.
- JSON doesn't have namespaces. Every object is a namespace: its set of keys is independent of all other objects, even exclusive of nesting. JSON uses context to avoid ambiguity, just as programming languages do.
- JSON has no validator. Being well-formed and valid is not the same as being correct and relevant. Ultimately, every application is responsible for validating its inputs.JSON Examples
"Drinks": ["Water", "Beer", "Vine"]
"complaint": "Blured night vision"
Advanced ETL Processor JSON Transformations
|Visit JSON Wiki Page|