Closed bhanurz closed 2 years ago
@stewartbryson Hello, hope you are well. Please check the above when possible and let me know if provided fix addresses the issue. Once acknowledged from your end, I will work on any refactoring and tests required in the PR. Thank you.
I merged the PR and a new release was generated. If works, can you close the issue?
Thanks so much for your contribution.
@stewartbryson Thanks for quick turn around on providing a release. Tested on my end, working as expected. Closing the issue.
Describe the bug Connector creation and drop queries fail. Sample query:
Connector creation fails with following error:
Note that it tries to drop the connector even if it does not exist.
Drop connector results in following error:
To Reproduce Steps to reproduce the behavior:
Expected behaviour Connector queries should execute successfully.
Additional context Following fix was done to validate the issue: https://github.com/RedPillAnalytics/gradle-confluent/pull/119
In getSourceDescription, following is used to return status of connector:
However, it should be as follows because an array is return by KSQL:
Using
.status
on an ArrayList causes it to return a list which is non null:[null]
. This subsequently leads to the condition add to check object existence to pass.Other failures are due to no command ID present for connector query executions so logic related to command ID should not be executed for connectors.