jcustenborder
Fix indentation in compose.yml
docker-compose fails due to broken indentation - more broadly I'm wondering if this should include a connect cluster?
Thinking about it a connect cluster might not be a great benefit. In my other projects I don't include one. I use the JVM I'm debugging as be the connect cluster. We could remove it. Thanks for the pull.
Oh right, I'm exploring kafka connect for the first time and trying to figure out a decent dev workflow for testing and debugging, if you have any tips (a README somewhere perhaps?) It would be good to know. My working assumption was that you would need a cluster to host the compiled connector, but I guess this is what connect-standalone is doing for you, which makes sense. I'm not overly keen to install the confluent platform locally though, I'd rather keep dev deps in docker, perhaps there is some way I can build a container with the confluent platform ready to boot.
It's up to you. Disclaimer I work for Confluent so installing Confluent isn't a thing for me. Personally I like having the kafka tools in my path so I leverage that. I download the tar.gz installation and extract it to /Users/jeremy/Library/confluent/ on my mac. Then I symlink the latest version to /Users/jeremy/Library/confluent/latest My ~/.bashrc file looks like this.
export CONFLUENT_HOME='/Users/jeremy/Library/confluent/latest'
export PATH="$PATH:/Applications/VMware Fusion.app/Contents/Library/VMware OVF Tool/:$CONFLUENT_HOME/bin"
I mainly have $CONFLUENT_HOME set so I can cd into the directory to edit the logging settings.
Now I can use scripts like this one I use standalone for development because it allows me to start the process and the connector I'm working on at the same time. From there it's the standard Remote JVM Debug configuration pointing to port 5005. Take a look at kafka-run-class for all of the settings you can change. If you look at the above script you'll see me passing in something to debug memory utilization.