-
-
Notifications
You must be signed in to change notification settings - Fork 200
Open
Labels
aiarchitectureArchitecture related issuesArchitecture related issuescoreCore framework functionalityCore framework functionalityenhancementNew feature or requestNew feature or request
Description
Implement Pipeline IPC and Remote Execution Routing
Goal
Enable the App Worker's Pipeline instance to seamlessly execute its counterpart inside the Data Worker.
Context
In issue #9451, we created Neo.data.Pipeline which handles instantiating a mirror of itself in the Data Worker if workerExecution: 'data' is set. However, calling pipeline.read() currently does nothing remotely. We need to implement the IPC messaging that triggers the remote execution.
Acceptance Criteria
- Implement
read(),create(),update(), anddestroy()methods onNeo.data.Pipeline. - When invoked in the App Worker with
workerExecution: 'data', these methods must send an IPC message (e.g.,{ action: 'pipeline.execute', id: this.remoteId, operation: 'read', params: ... }) to the Data Worker. - Add an
onPipelineExecutemessage handler insrc/worker/Data.mjs. - This handler must look up the correct Pipeline instance from
this.instances, invoke the requested operation (which will run the local Connection, Parser, and Normalizer in the Data Worker), and then send the finalized record array back to the App Worker's Promise resolver.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
aiarchitectureArchitecture related issuesArchitecture related issuescoreCore framework functionalityCore framework functionalityenhancementNew feature or requestNew feature or request