TableSink should ensure that the schema only has simple types, during deployment of adapter.
If a TableSink has a non-simple type, then during runtime of the pipeline, the pipeline will fail with the error:
Additionally, explore fails on the table created for it:
This is a mis-leading error. When the output schema of the table sink doesn't match the input schema we see the same error. We need to improve the error handling to show appropriate errors to the users.