bossenti commented on issue #2106: URL: https://github.com/apache/streampipes/issues/2106#issuecomment-1809622408
sounds like a great plan! Just generally, since this is a change that affects the end user directly (although only positively), I would really appreciate so see some documentation & and E2E test once the workaround is in place. That would be awesome 🙂 With respect to the reminder: Please be aware that sinks (and processing elements as well) can define a `requiredStream` within their `declareConfig()` method. Would be great if we could solve it this way. (Maybe you are already aware of it, but just to mention). In this case, we would need to check how we handle the automatic pipeline creation. Out of my thoughts, I would suggest stopping & flagging the pipeline and setting a corresponding notification within the pipeline. If you have any problems, finding the specific functionalities, feel free to reach out 🙂 Or, of course, if you have any other ideas, I'm happy to discuss it -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@streampipes.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
