-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
implement migration for adapter and pipeline element configurations #2077
implement migration for adapter and pipeline element configurations #2077
Conversation
…on-for-adapter-and-pipeline-element-configurations # Conflicts: # ui/projects/streampipes/platform-services/src/lib/model/gen/streampipes-model.ts # ui/src/app/add/components/endpoint-item/endpoint-item.component.ts # ui/src/scss/sp/main.scss
…pter-and-pipeline-element-configurations' into 2045-implement-migration-for-adapter-and-pipeline-element-configurations # Conflicts: # streampipes-extensions-api/src/main/java/org/apache/streampipes/extensions/api/migration/AdapterMigrator.java # streampipes-extensions-api/src/main/java/org/apache/streampipes/extensions/api/migration/MigrationResult.java # streampipes-extensions-api/src/main/java/org/apache/streampipes/extensions/api/migration/ModelMigrator.java # streampipes-extensions-management/src/main/java/org/apache/streampipes/extensions/management/model/SpServiceDefinition.java # streampipes-extensions-management/src/main/java/org/apache/streampipes/extensions/management/model/SpServiceDefinitionBuilder.java
…on-for-adapter-and-pipeline-element-configurations
This reverts commit 646e792.
if (obj instanceof ModelMigrator<?, ?>) { | ||
return this.config().equals(((ModelMigrator<?, ?>) obj).config()); | ||
} | ||
return false; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just out of curiosity, where is this equals
method used? Is this the only reason the AdapterMigrator
has to be an abstract class instead of an interface?
streampipes-client/src/main/java/org/apache/streampipes/client/api/AdminApi.java
Outdated
Show resolved
Hide resolved
streampipes-model/src/main/java/org/apache/streampipes/model/graph/DataProcessorInvocation.java
Outdated
Show resolved
Hide resolved
streampipes-model/src/main/java/org/apache/streampipes/model/graph/DataSinkInvocation.java
Outdated
Show resolved
Hide resolved
@bossenti Is there a reason why we have two endpoints at the core side for managing migrations of adapters and pipeline elements? |
I created a PR which breaks down the migration into smaller code units and creates a single request from extensions to core for submitting migration configs: #2101 |
* Extract MigrationResource logic into smaller units * Use single request for submitting migrations from extensions to core * refactor: remove dead code * style: change formatting --------- Co-authored-by: bossenti <[email protected]>
@dominikriemer you already addressed all your comments in your PR #2101, right? |
…on-for-adapter-and-pipeline-element-configurations # Conflicts: # streampipes-model/src/main/java/org/apache/streampipes/model/base/InvocableStreamPipesEntity.java
@bossenti I didn't address the comments above - do you know where the equals method is used from the |
@dominikriemer Yes it is. We use it to determine if a migration has already been registered at the extensions service so that we can't register the same migration multiple times. |
Purpose
see #2045
See detailed explanation
Remarks
PR introduces (a) breaking change(s): no
PR introduces (a) deprecation(s): yes
Deprecations
create()
methods ofProcessingElementBuilder
that do not contain a versioncreate()
methods ofAdapterConfigurationBuilder
that do not contain a version