tenthe commented on issue #2094: URL: https://github.com/apache/streampipes/issues/2094#issuecomment-2311644356
Hi @IsaakKrut, to your first question. I would say that the adapter should be stopped if it cannot be migrated. So if this has not been done yet, I would suggest implementing this. Regarding the second question: I think it is good that it is logged. However, the logs are not shown to the user in the UI, so it's not obvious to the user. It would be cool to have a similar mechanism in the adapter overview as we have for pipelines to indicate problems. For adapters, the status currently only shows whether the adapter is running or not:  Pipelines have a health status (`PipelineHealthStatus`) which is used to indicate problems to the user, maybe we can do something similar for adapters here and indicate to the user that the migration has failed and some manual work needs to be done to fix it. The UI code for the pipelines is in `PipelineOverviewComponent` and for the adapters `ExistingAdaptersComponent`. What do you think of this? If you are interested in implementing this, let me know, I can also try to help you if you have any problems. Cheers, Philipp -- 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
