uchennakevinm1

Reduce the number of enter characters for the name of connectors and pipelines which the user can use Actual result:  • layout is broken • the user can enter an...

The error {"code":9,"message":"failed to delete pipeline: pipeline has connectors attached"} isn’t documented in [Swagger](http://localhost:8080/openapi/#/PipelineService/PipelineService_DeletePipeline) /v1/pipelines/{id} Request Method: DELETE 400 message: "failed to delete pipeline: pipeline has connectors attached"

- The user isn't informed about the error in UI after occurring the error during the data transfer process - The user can't stop the pipeline running after the system...

The error {"code":9,"message":"failed to delete pipeline: pipeline has connectors attached"} isn’t documented in [Swagger](http://localhost:8080/openapi/#/PipelineService/PipelineService_DeletePipeline) /v1/pipelines/{id} Request Method: DELETE 400 message: "failed to delete pipeline: pipeline has connectors attached"

[Setting pipelines] Make the "Save Changes" button inactive after saving update of a pipeline name or description. Argument: The user mayn't understand whether the change has been saved or not.

All errors are handled as 500 For example:  • Request /v1/pipelines/{{pipeline_id}}/start is returned code 500 after trying start the pipeline which don't have connectors or have only 1 connector message:...

What happens to our message delivery and ordering guarantees during various failure scenarios. Fixed number of failure scenarios: 1. Upstream resource failure 2. Connector Failure / Error - Bug in...