...
| Issue | Affected Source/Sink/Transform | Caused by (if known) | JIRA (if existing) | Error message | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Importing a pipeline needs users to click on nodes to populate schema | ALL |
| ||||||||||||
| Getschema for DB plugins should honor the column case configuration | DB Plugins |
| ||||||||||||
| Error messages from plugins should have the plugin name, version and scopeError messages from plugins should have the plugin name, version and scope |
| |||||||||||||
| Schema requirement of plugins is not visible to users |
|
| ||||||||||||
| If a plugin throws an exception, the pipeline fails without logging the error |
| |||||||||||||
| Hydrator pipeline fails at runtime when external sink has the same name as native sink | Pipeline with TPFS sink (called output) and HDFS sink with external name called output |
| java.lang.IllegalArgumentException: An external sink cannot have the same name as an existing CDAP Dataset instance output | |||||||||||
...