[KAFKA-159] Support dynamic collection naming strategies Created: 21/Sep/20 Updated: 28/Oct/23 Resolved: 08/Feb/21 |
|
| Status: | Closed |
| Project: | Kafka Connector |
| Component/s: | Sink |
| Affects Version/s: | None |
| Fix Version/s: | 1.4.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ross Lawley | Assignee: | Ross Lawley |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Epic Link: | KAFKA-47 | ||||||||||||
| Documentation Changes: | Needed | ||||||||||||
| Documentation Changes Summary: | Dynamic Namespace Mapping for the Sink Added a new interface `com.mongodb.kafka.connect.sink.namespace.mapping.NamespaceMapper` with a `getNamespace` method. The sink connector includes two implementations:
The following configuration options can help configure namespace mapping:
|
||||||||||||
| Description |
|
Currently the strategy for where data is saved by the Sink connector is based upon the topics' database and collection configuration. This maps the data from each topic to a single collection. Some users would like to dynamically create the collection to save the data into based upon the value in a SinkRecord. Examples could be:
Users should also be able to write their own collection naming strategy class and include it to allow for full customizability. |
| Comments |
| Comment by Githook User [ 08/Feb/21 ] |
|
Author: {'name': 'Ross Lawley', 'email': 'ross.lawley@gmail.com', 'username': 'rozza'}Message: Added Dynamic Namespace Mapping for the Sink Added a new interface `NamespaceMapper` with a `getNamespace` method. The sink connector includes two implementations:
|