Description This recipe demonstrates how to ensure a recipe complete when nested data structures are used with inline() or explode() functions. The key is to attach a schema to the connector that defined the temporarily non-existant value that Spark will otherwise drop the column for (because it's all null)
Note: we are looking for an endOn date that doesn't exist in this payload but could. Use schema to ensure that the field is available even if null.