Skip to content
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

feat: DataFlowManager and DataFlowController refactoring #3917

Merged

Conversation

wolf4ood
Copy link
Contributor

@wolf4ood wolf4ood commented Feb 23, 2024

What this PR changes/adds

DataFlowManager , DataFlowController and DataPlaneClient methods for staring a new data flow were refactor according the term used in the data plane signaling spec.

Additionally now the DataFlowResponse may contain the dataPlaneId selected for the transfer that will be stored
into the TransferProcess when transitioning to the started state. This will allow to punctually deliver subsequent message to the right data plane. If no dataPlaneId is not present the behaviour is the same as before.

Additionally the tracked flag has been removed in the dataplane.

The suspend is not introduced in this PR since it will first need support in the DataPlane and in the DSP protocol implementation #3350

Why it does that

data plane signaling

Closes #3899

Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

@wolf4ood wolf4ood self-assigned this Feb 23, 2024
@wolf4ood wolf4ood added refactoring Cleaning up code and dependencies enhancement New feature or request labels Feb 23, 2024
*/
@NotNull
StatusResult<DataFlowResponse> initiateFlow(TransferProcess transferProcess, Policy policy);
StatusResult<DataFlowResponse> start(TransferProcess transferProcess, Policy policy);

Check notice

Code scanning / CodeQL

Useless parameter Note

The parameter 'policy' is never used.
@wolf4ood wolf4ood force-pushed the feat/3899_data_flow_controller_refactor branch 2 times, most recently from 35e2f37 to 0425d8d Compare February 23, 2024 18:00
@wolf4ood wolf4ood force-pushed the feat/3899_data_flow_controller_refactor branch 3 times, most recently from d83e438 to e1e06ea Compare February 23, 2024 18:19
@wolf4ood wolf4ood force-pushed the feat/3899_data_flow_controller_refactor branch from e1e06ea to 4aa29de Compare February 23, 2024 18:23
@Override
public Builder self() {
return this;
}

public DataPlaneManagerImpl build() {

Check notice

Code scanning / CodeQL

Missing Override annotation Note

This method overrides
Builder<DataFlow,DataPlaneStore,DataPlaneManagerImpl,Builder>.build
; it is advisable to add an Override annotation.
@wolf4ood wolf4ood marked this pull request as ready for review February 26, 2024 12:39
@wolf4ood wolf4ood added the dpf Feature related to the Data Plane Framework label Feb 26, 2024
Copy link
Member

@ndr-brt ndr-brt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd add the breaking change label as there are changes in the SQL schema

@wolf4ood wolf4ood added the breaking-change Will require manual intervention for version update label Feb 26, 2024
@wolf4ood wolf4ood merged commit 0f74889 into eclipse-edc:main Feb 26, 2024
23 checks passed
@wolf4ood wolf4ood deleted the feat/3899_data_flow_controller_refactor branch February 26, 2024 16:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change Will require manual intervention for version update dpf Feature related to the Data Plane Framework enhancement New feature or request refactoring Cleaning up code and dependencies
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DPS: DataFlowController and DataFlowManager refactor
4 participants