Issues

Implement Program Failure Exception Handling in Snowflake Source/Sink plugin to catch known errors and bug fixes

Add validation to check configured output schema with input schema for spanner sink

Plugin preferences- field validation and error messages

Plugin Stage Level Validation

Improve error message in database source when there is a schema mismatch

Surface appropriate error messages in validator transform

Strange error from Dataprep file connection

Fix error message for an when a database connection cannot be opened or tested

CDAP components should expose errors

Plugin deployment should fail if the dependencies exported is not found in the artifact

Error message when failure to add tag should be meaningful

Data prep CSV parsing error needs to be more user friendly

Hydrator error not clear - java.lang.IllegalStateException

Audit publishing when Kafka is down

Router should not print a stacktrace when a service is not discoverable

When YARN doesn't run CDAP apps, this should be surfaced to the user

On multinode cluster if the clocks are not in sync an ETL pipeline fail with not a very helpful message

CDAP should show a warning in UI on insufficient resources to launch a job

TableSink should ensure that the schema only has simple types, during deployment of adapter

Unnecessary logging on failure to clean up tmp directory

Noticed a weird error in UI: Error Sending error: Error: http status 0

Service errors are difficult to debug

HttpExceptionHandler should handle FORBIDDEN exceptions.

HBaseQueueDebugger throws NotFoundException when a newly deployed app is not yet started

Misleading DEBUG message in Standalone

Workflow's inner program has improper stop REST API behavior

cdap-cli create stream should indicate when stream already exists

Warning everytime you start Standalone about Notification system unable to publish.

Frequent InterruptedExceptions when stopping stopping runnables during integration tests on a cluster

Failure to create directory should show directory name

Better error handling for deploy pipeline

Running explore query on TPFS Parquet Dataset with Map as one of the fields throws an exception in the Explore service

Backend is logging excessively

Dataset Framework throws NotFoundExn without logging or returning the actual error

Throw a validation error when workflow contains an anonymous inner class as Predicate/Custom Action

ProgramLifeCycleHttpHandler/Service and DefaultStore need better error handling

After less than a day, CDAP cluster runs out of disk space

Fixing wrong/bad error messages

Services return the same message for all failures: Transaction Failure when committing changes

Improve error handling across CDAP