TableSink should ensure that the schema only has simple types, during deployment of adapter
Description
Release Notes
None
Attachments
1
is duplicated by
relates to
Activity
Show:
Shankar Selvam January 7, 2016 at 7:05 PM
This should be fixed as a part of this ,
https://issues.cask.co/browse/CDAP-4456
Sreevatsan Raman October 22, 2015 at 12:51 AM
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.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Shankar SelvamReporter
Ali AnwarLabels
Affects versions
Components
Fix versions
Priority
MajorCreated October 15, 2015 at 11:42 PM
Updated January 7, 2016 at 7:05 PM
Resolved January 7, 2016 at 7:05 PM
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: