Skip to content
This repository was archived by the owner on Apr 22, 2022. It is now read-only.

Pushing records to ALL kafka sinks #483

@josephwibowo

Description

@josephwibowo

I'm a little confused as to the behavior of Kafka sinks. It seems that when an event is created, the event is pushed to all sinks. In the case of Kafka, this pushes the event to all Kafka sinks even though the event is only relevant to one sink. Am I missing something? Why wouldn't it be smart enough only to push the event to the relevant Kafka sink?

Example:

mappings {
    t1 = {
      sources = [browser]
      sinks = [t1]
      confluent_id = 1
    }

    t2 = {
      schema_file = "/opt/divolte/divolte-collector/conf/avro/t2.avsc"
      mapping_script_file = "/opt/divolte/divolte-collector/conf/mapping.groovy"
      sources = [browser]
      sinks = [t2]
      confluent_id = 2
    }
  }

sinks {
    t1 {
      type = kafka
      mode = confluent
      topic = t1
    }

    t2 {
      type = kafka
      mode = confluent
      topic = t2
    }
  }

t1 events will write to t1 and t2 sinks. t2 events will write to t1 and t2 sinks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions