You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if (transferProcess.getDataRequest().isManagedResources()) {
monitor.warning(format("No checker found for process %s. The process will not advance to the COMPLETED state.", transferProcess.getId()));
returnfalse;
} else {
//no checker, transition the process to the COMPLETED state automatically
transitionToCompleting(transferProcess);
}
returntrue;
why do we have different behavior based on different resource types (managed or not)?
My gut feeling would say that we shouldn't change the transfer status if we don't have any knowledge, leaving this duty to an external service that can do it by calling the /complete api on the management-api.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
After a transfer has been started, the manager iterates over it to see if has been completed or not, it does that using a
StatusChecker
service.If no
StatusChecker
is available currently we have two different behavior described by this piece of code:Connector/core/control-plane/transfer-core/src/main/java/org/eclipse/edc/connector/transfer/process/TransferProcessManagerImpl.java
Lines 504 to 511 in 7eee479
why do we have different behavior based on different resource types (managed or not)?
My gut feeling would say that we shouldn't change the transfer status if we don't have any knowledge, leaving this duty to an external service that can do it by calling the
/complete
api on the management-api.thoughts?
Beta Was this translation helpful? Give feedback.
All reactions