[KAFKA-372] custom header with MongoDB Source Connector Created: 24/May/23 Updated: 27/Oct/23 Resolved: 15/Jun/23 |
|
| Status: | Closed |
| Project: | Kafka Connector |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Harish Sharma | Assignee: | Robert Walters |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Hi Team, I am trying to add a custom header using following config but as mentioned that property not belong to managed connector. Please can you suggest how can we add a custom header. |
| Comments |
| Comment by PM Bot [ 15/Jun/23 ] |
|
There hasn't been any recent activity on this ticket, so we're resolving it. Thanks for reaching out! Please feel free to reopen this ticket if you're still experiencing the issue, and add a comment if you're able to provide more information. |
| Comment by PM Bot [ 06/Jun/23 ] |
|
Hi waytohksharma@gmail.com! If this is still an issue for you, please open Jira to review the latest status and provide your feedback. Thanks! |
| Comment by Robert Walters [ 30/May/23 ] |
|
The transform and HeaderFrom is an SMT and part of the Kafka Connect framework. This feature has nothing to do with the MongoDB Connector. You will have to file a support ticket with AWS as it is their implementation of Kafka Connect within AWS MKS that is having the issue. I know Confluent Cloud doesn't support this particular transform with their hosted connectors so perhaps there is some issue with it in AWS as well. |
| Comment by Harish Sharma [ 26/May/23 ] |
|
robert.walters@mongodb.com This is I am trying with AWS MSK Connect with Mongo Source Connector vlatest |
| Comment by Robert Walters [ 25/May/23 ] |
|
waytohksharma@gmail.com are you trying to you this within the Confluent Cloud's Atlas Source connector? |
| Comment by PM Bot [ 24/May/23 ] |
|
Hi waytohksharma@gmail.com, thank you for reporting this issue! The team will look into it and get back to you soon. |