Auto-load connectors from directory
See original GitHub issueRelated to confluentinc/cp-docker-images#460
Should add some directory in kafka-connect-base
that loads .json
or .properties
files on start.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:20
- Comments:15 (1 by maintainers)
Top Results From Across the Web
Developing a Connector - IBM
All Tivoli® Directory Integrator Connectors implement the " com.ibm.di.connector ... it will automatically load the new Connector and make it ready for use....
Read more >Autoload classes from different folders - php - Stack Overflow
This autoloader is a direct 1:1 mapping of class name to directory structure; the namespace is the directory path and the class name...
Read more >What is Auto Loader? | Databricks on AWS
Auto Loader provides a Structured Streaming source called cloudFiles . Given an input directory path on the cloud file storage, the cloudFiles ...
Read more >Databricks Autoloader: Data Ingestion Simplified 101 - Learn
cloudFiles.allowOverwrites: With the default value set as true, this decides whether to permit input directory file changes to overwrite ...
Read more >Why isn't the scripts in my autoload folder being executed in ...
I assumed "autoload" meant that the script would be loaded on startup, which is exactly what the plugin folder is for. As for...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks - this was helpful! I prefer a slightly optimized version:
Changes over the above version:
curl
once per iteration - no need to call it a second time just for printing the status. Also only one place to change the hostname and port.200
instead of a status different than000
. I’ve had Connect return a404
status during startup (since the HTTP port was up, but the endpoint was not deployed yet), in which case thecreate-connectors.sh
script failed. Waiting for200
ensures that theconnectors
endpoint is available.netcat
call - not sure what that was needed for. Looks like a leftover from a previous version of the script…FWIW, I run this from a separate service in my Docker Compose file - the image I use is
appropriate/curl:latest
. That way, you don’t have to start therun
command in the background…One alternative, as shown by @rmoff
In the compose, override the container command