Lists all of the enrichment strategies supported by this Nakadi installation.
Lists all of the enrichment strategies supported by this Nakadi installation. Special or custom strategies besides the defaults will be listed here.
The flow id of the request, which is written into the logs and passed to called services. Helpful for operational troubleshooting and log analysis.
Returns a list of all enrichment strategies known to Nakadi
Lists all of the partition resolution strategies supported by this installation of Nakadi.
Lists all of the partition resolution strategies supported by this installation of Nakadi. Special or custom strategies besides the defaults will be listed here.
Nakadi currently offers these inbuilt strategies:
org.zalando.kanadi.api.PartitionStrategy.Random: Resolution of the target partition happens randomly (events are evenly distributed on the topic's partitions). org.zalando.kanadi.api.PartitionStrategy.UserDefined: Target partition is defined by the client. As long as the indicated partition exists, Event assignment will respect this value. Correctness of the relative ordering of events is under the responsibility of the Producer. Requires that the client provides the target partition on org.zalando.kanadi.api.Metadata.partition (See org.zalando.kanadi.api.Metadata). Failure to do so will reject the publishing of the org.zalando.kanadi.api.Event. org.zalando.kanadi.api.PartitionStrategy.Hash: Resolution of the partition follows the computation of a hash from the value of the fields indicated in the EventType's org.zalando.kanadi.api.EventType.partitionKeyFields, guaranteeing that Events with same values on those fields end in the same partition. Given the event type's category is DataChangeEvent, field path is considered relative to "data".
The flow id of the request, which is written into the logs and passed to called services. Helpful for operational troubleshooting and log analysis.
Returns a list of all partitioning strategies known to Nakadi