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:
- Use a date based field as the basis for the collection naming to allow bucketing of data into MongoDB
- Use a string field directly for the collection naming strategy
Users should also be able to write their own collection naming strategy class and include it to allow for full customizability.
- related to
-
KAFKA-186 Support dot notation lookups in dynamic topic mapping
- Closed