Kafka
Kafka connector enables seamless data exchange with both Apache Kafka and Confluent Kafka, which are distributed publish/subscribe messaging systems. The connector provides a unified, high-throughput, and low-latency platform for managing data Streams effectively. Using the Kafka connector, you can create actions and run various operations, such as retrieving data from or inserting data into Kafka topics.
Kafka connector consists of the following two components.
- Account
- Facilitates the connection with Apache Kafka or Confluent Kafka servers. Configuring an account is essential to run any operation through Kafka actions.
- Actions
- Facilitates to produce and consume messages from Kafka topics. Actions are based on templates that are provided by the Kafka connector. Each action represents a specific task that is run on a resource, such as using the Produce action to publish a message to a specified Kafka topic.
Limitations
- Security protocol transition limitations when editing an Apache Kafka account
- To edit an Apache Kafka account, the mentioned security protocols restrict the protocol
flexibility and must be considered during the account configuration.
- If the security protocol is set to PLAINTEXT, you cannot switch to any other modes (SASL_PLAINTEXT, SASL_SSL, or SSL).
- If the security protocol is set to SASL_PLAINTEXT, SASL_SSL, or SSL, you can switch to any of these three modes but not to PLAINTEXT.
- Schema Information modal limitation
- In Confluent Kafka services, the Schema Information modal does not retrieve schema details, including the overview, content, and subject–version mappings.