A partner posts one JSON object per payment. Some of them are not JSON at all, and the pipeline must not stop because of it.

Input

A well-formed body looks like {"amount": 10.5, "currency": "INR"}.

Output

Every input row, with the columns:

• record_id
• status — 'VALID' or 'INVALID'
• amount — the parsed amount on a valid row, null otherwise
• currency — the parsed currency on a valid row, null otherwise

A row is VALID only when the body parses and both fields carry a value. Anything else is INVALID and carries neither field forward.

Example

Constraints

• Declare the schema. Inferring it means reading the data first, and makes the output columns depend on which payloads happened to arrive.
• Parsing is not validation. {"amount": 10.5} parses perfectly well.
• 0.0 is an amount. A JSON null is not.
• Nothing may throw. A batch of entirely unparseable bodies is a normal batch.
• Row order is not graded. Column names and their order are.