GridGain vs. Ignite Kafka Connector
Compares the open source Apache Ignite Kafka Connector with the GridGain Kafka Connector feature by feature.
Open source Apache Ignite includes a different Ignite Kafka Connector implementation than GridGain. The table below compares Open Source Ignite and GridGain Kafka Connectors.
Scalability
Limited Source connector is not parallel. Sink connector is parallel.
Source connector creates a task per cache. Sink connector is parallel.
At least once processing semantics
NO Source data might be lost during connector restart or rebalancing.
YES Source connector can be configured to resume from the last committed offset.
Exactly once processing semantics
NO
YES
Preserving source data schema
NO
YES
Handling multiple caches
NO
YES Connector can be configured to handle any number of caches.
Dynamic Reconfiguration
NO
YES Source connector detects added or removed caches and re-configures itself.
Initial Data Load
NO
YES
Handling data removals
YES
YES
Serialization and Deserialization of data
YES
YES
Filtering
Limited Only source connector supports a filter.
Both source and sink connectors support filters.
Transformations
Kafka SMTs
Kafka SMTs
DevOps
Some free-text error logging.
Health Model defined.
Support
Apache Ignite Community
Supported by GridGain, certified by Confluent.
Packaging
Uber JAR
Connector Package
Deployment
Plugin PATH on all Kafka Connect workers.
Plugin PATH on all Kafka Connect workers. CLASSPATH on all GridGain nodes.
Kafka API Version
0.10
2.0
Source API
Ignite events
Ignite continuous queries
Sink API
Ignite data streamer
Ignite data streamer
This page is: Copyright © 2026 MariaDB. All rights reserved.
Last updated
Was this helpful?

