Can you include the stack trace rather than a screenshot? We can’t see which class appears to be missing.
> On 2 Jul 2023, at 17:04, Tama MA <tam...@tamama.io> wrote: > > Hi Ignite community, > > Per instructed by Ignite documentation (Streaming Data via Kafka Connect) > https://ignite.apache.org/docs/latest/extensions-and-integrations/streaming/kafka-streamer > > 0) My versions are: > - Apache Ignite 2.15.0 > - Apache Kafka 3.4.1 > > 1) I downloaded the JAR - org.apache.ignite:ignite-kafka-ext:1.0.0. > (compiled against Ignite 2.9.x) > 2) I added this to kafka-connect properties file: > > plugin.path=libs/connect-file-3.4.1.jar,/home/tamama/.m2/repository/org/apache/ignite/ignite-kafka-ext/ignite-kafka-ext-1.0.0.jar > > > 3) As usual, I apply Kafka Connect > > > PUT /connectors/gnite-sink-toto-1/config > { > "name": "ignite-sink-toto-1", > "connector.class": > "org.apache.ignite.stream.kafka.connect.IgniteSinkConnector", > "tasks.max": 1, > "topics": "nginx__access__private_tamama_io", > "cacheName": "toto-tamama-1", > "cacheAllowOverwrite": true, > "igniteCfg": > "/home/tamama/.tamama/etc/kafka/connect/ignite-sink/ignite-rsyslog-ignite-47500.xml" > } > > > 4) This crashes: > > <PastedGraphic-1.png> > > > Questions? > > Q1) It seems to me that Ignite is discontinuing on Kafka integration efforts. > May I ask if this is generally true? > - Maybe in this case, we could remove the extension in the > documentation, as this would confuse the users? > > Q2) If this were to be made to work, I believe that we need to A) compile the > source code (ignite-kafka-ext) against latest ignite-core:2.15, B) compile > into a fat-jar. (Uber-jar). Otherwise, I would need to use CLASSPATH which > would be a bit in a mess…. ? > > However, if the general consensus is to stay away from Ignite-Kafka, I would > be glad to accept this too. :) > > Kind regards, > Tama MA
