[KAFKA-264] post.processor.chain ignored in conflent cloud connector Created: 08/Nov/21 Updated: 27/Oct/23 Resolved: 14/Mar/22 |
|
| Status: | Closed |
| Project: | Kafka Connector |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Unknown |
| Reporter: | Denis Collumbien | Assignee: | Robert Walters |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | external-user | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
The post.processor.chain is ignored when used in the confluent cloud connector. During the configuration, the field is correctly validated, but it is not used. We tried: post.processor.chain | com.mongodb.kafka.connect.sink.processor.KafkaMetaAdder |
| Comments |
| Comment by PM Bot [ 14/Mar/22 ] |
|
There hasn't been any recent activity on this ticket, so we're resolving it. Thanks for reaching out! Please feel free to comment on this if you're able to provide more information. |
| Comment by Robert Walters [ 17/Nov/21 ] |
|
it@trustbuilder.com Can you send the complete configuration ? Thanks will forward this to Confluent as we don't own the Confliuent Atlas Source/Sink |
| Comment by Esha Bhargava [ 11/Nov/21 ] |
|
it@trustbuilder.com Thank you for reporting the issue! We'll look into it and get back to you soon. |