I’d like to say I’m using cp-all-in-one, but some how did not work for me. could not get things working, as for the labs I was trying to do.
but in the end got the kafka-to-elastic working thats part of demo-scene drop.
I did add the control-centre to the docker-compose.yml.
now want to add the datagen container. planning on using the below, as pulled from the cp-all-in-one docker-compose.yml.
question though, never having interfaced with dotage before.
how do I interface with it, looking at the newest video by Confluent/Elastic they manage it as a connector, where they decide what type of data to generate, etc, adding this as a datagen image, does not make me think I will interface with it as if it is a connector.
G
ksql-datagen:
image: confluentinc/ksqldb-examples:6.2.0
hostname: ksql-datagen
container_name: ksql-datagen
depends_on:
- ksqldb-server
- broker
- schema-registry
- connect
command: "bash -c 'echo Waiting for Kafka to be ready... && \
cub kafka-ready -b broker:29092 1 40 && \
echo Waiting for Confluent Schema Registry to be ready... && \
cub sr-ready schema-registry 8081 40 && \
echo Waiting a few seconds for topic creation to finish... && \
sleep 11 && \
tail -f /dev/null'"
environment:
KSQL_CONFIG_DIR: "/etc/ksql"
STREAMS_BOOTSTRAP_SERVERS: broker:29092
STREAMS_SCHEMA_REGISTRY_HOST: schema-registry
STREAMS_SCHEMA_REGISTRY_PORT: 8081
all of this would/could be easier as an alternate option if I could deploy the ElasticSearch Sink connector into the CP-all-in-one 6.2 docker-compose.yml build.
actually very simple I don’t know how to add the ElasticSearch connector capability to the shipped images.
sadly allot of new tech flying at my head… and it’s getting muddled, hehehe.
would be/could be nice to have the cp-all-in-one include commented out sections to be able to uncomment to extend it, like add this sink connector, or the datagen connector.
I don’t know how to add the ElasticSearch connector capability to the shipped images.