Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[The Pipeline detail screen]  400 error is handled when creating the Kafka Destination connector with optional configuration ... #600

Closed
uchennakevinm1 opened this issue Aug 25, 2022 · 5 comments
Assignees

Comments

@uchennakevinm1
Copy link
Contributor

[The Pipeline detail screen]  400 error is handled when creating the Kafka Destination connector with optional configuration "acks": "0" or "acks": "1"
Bug is only reproduced when using the UI conduit
 
Additional info: We can create the Kafka Destination connector with optional configuration "acks": "0" or "acks": "1" by using Postman

Logs: 2022-05-06T15:37:53+00:00 ERR error processing HTTP request error="rpc error: code = InvalidArgument desc = proto:\u00a0(line 1:167): invalid value for string type: 0" http_endpoint="POST /v1/connectors" request_id=44de8178-6732-4967-a264-792fc8c4aa71 stack=null
2022-05-06T15:39:10+00:00 ERR error processing HTTP request error="rpc error: code = InvalidArgument desc = proto:\u00a0(line 1:167): invalid value for string type: 1" http_endpoint="POST /v1/connectors" request_id=7f409e72-c3db-41df-a6d6-4d7d5155b06f stack=null

@jmar910
Copy link
Member

jmar910 commented Sep 26, 2022

@uchennakevinm1 @hariso I am unable to reproduce this, can we confirm this is still an issue with a proper kafka setup?

@uchennakevinm1 uchennakevinm1 removed the status in Conduit Main Oct 19, 2022
@artemklevtsov
Copy link

artemklevtsov commented Aug 31, 2023

Same here with postgres destination. I tried to fill table field.
изображение
Log from the container:

2023-08-31T16:50:23+00:00 ERR error processing HTTP request error="rpc error: code = InvalidArgument desc = proto:\u00a0(line 1:139): invalid value for string type: {" http_endpoint="PUT /v1/connectors/bf462fea-1d1d-48cd-b46a-de1a6d7a0d41" request_id=7e257f83-dc5b-4244-b5c3-50323dcad0e5 stack=null

@hariso
Copy link
Contributor

hariso commented Sep 1, 2023

@artemklevtsov Thanks for the details! Which version of Conduit are you running?

Based on the logs which you've shown, it looks like the UI is getting confused by the parameter names. The configuration should have:

{
  "sdk.record.format": "debezium/json"
}

and not:

{
  "sdk.record": {
    "format": "debezium/json"
  }
}

Meanwhile, if this is a blocker for you, I can suggest using a pipeline configuration file. That should definitely work.

@artemklevtsov
Copy link

@artemklevtsov Thanks for the details! Which version of Conduit are you running?

Latest stable release: e.g. v0.7.2.

@hariso hariso added the triage Needs to be triaged label Sep 5, 2023
@hariso hariso moved this to Triage in Conduit Main Sep 5, 2023
@simonl2002 simonl2002 removed the triage Needs to be triaged label Oct 2, 2023
@simonl2002 simonl2002 removed the status in Conduit Main Oct 2, 2023
@lovromazgon
Copy link
Member

UI will be deprecated soon, see #1911.

@lovromazgon lovromazgon closed this as not planned Won't fix, can't repro, duplicate, stale Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants