GitHub user dominikriemer added a comment to the discussion: Problems with extending StreamPipes with a new Data Processor
Thanks for the information. The pom version of your extensions file should match the StreamPipes version of the core, 0.92.0. The Consul warning should disappear after updating the version. Concerning the error upon pipeline start, I suggest to try the following: * Try to start a pipeline from the pre-installed elements (e.g., connect a machine simulator to the data lake sink) - does this work or do you also get an error? * If this is working, I think that the core (running in Docker) cannot properly access your locally running pipeline element (which seems to use the IP 172.27.30.183). The IP is usually auto-discovered when you start your custom service. Sometimes the auto-discovery chooses an IP which cannot be accessed from within the Docker network. You can try so by pinging to this IP from the core's Docker container. If you can't reach the IP from there, you can start your extensions service by manually providing an IP or hostname. This is done by providing an environment variable `SP_HOST` (to the extensions service you are developing). Please answer in case these ideas don't work for you. GitHub link: https://github.com/apache/streampipes/discussions/1768#discussioncomment-6427450 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
