Hi @bossenti, I'd like to learn more about migrations. I took a look at this issue and there is already logging in place in AdapterMigrationManager on line 108.
else { LOG.info( "Migration is not applicable for adapter '{}' because of a version mismatch - " + "adapter version: '{}', migration starts at: '{}'", adapterDescription.getElementId(), adapterVersion, migrationConfig.fromVersion() ); }
It was introduced as part of #2077 . However, the adapter is not stopped when the adapter's version is lower than the migrationConfig's fromVersion. It's stopped only when versions are equal and migration fails.

My questions are:

1. Should the adapter be stopped when its version is lower than the available migrations? What happens if it is not?
2. With logging already in place, can this issue be closed?

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