Struct InMemoryDataProvider 

pub struct InMemoryDataProvider { /* private fields */ }

Implementations

impl InMemoryDataProvider

pub fn new(owner_controller: ControllerId) -> InMemoryDataProvider

pub fn with_envelope( owner_controller: ControllerId, envelope: ExternalDataPlanEnvelope, ) -> Result<InMemoryDataProvider, DagMlError>

pub fn register_envelope( &mut self, envelope: ExternalDataPlanEnvelope, ) -> Result<(), DagMlError>

pub fn handle_record(&self, handle: u64) -> Option<DataHandleRecord>

pub fn handle_records(&self) -> Vec<DataHandleRecord>

pub fn view_record(&self, handle: u64) -> Option<DataViewHandleRecord>

pub fn view_records(&self) -> Vec<DataViewHandleRecord>

Trait Implementations

impl Debug for InMemoryDataProvider

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl RuntimeDataProvider for InMemoryDataProvider

fn materialize( &self, request: &DataMaterializationRequest, ) -> Result<HandleRef, DagMlError>

fn make_view(&self, request: &DataViewRequest) -> Result<HandleRef, DagMlError>

fn training_data_identity( &self, binding: &DataBinding, ) -> Result<Option<TrainingDataIdentity>, DagMlError>

Attest the exact feature and target content bound to one training input.

fn coordinator_relations( &self, binding: &DataBinding, ) -> Result<Option<SampleRelationSet>, DagMlError>

fn methods_pls_capability(&self) -> Result<(), DagMlError>

Confirm that this provider can supply the deliberately narrow numeric view consumed by the portable Methods PLS controller. The default is a refusal, so an ordinary data provider can never accidentally expose its buffers to a native numerical controller.

fn preflight_methods_pls( &self, request: &MethodsPlsDataRequest, ) -> Result<(), DagMlError>

fn methods_pls_data( &self, _request: &MethodsPlsDataRequest, ) -> Result<MethodsPlsData, DagMlError>

Return provider-selected row-major numeric values for a Methods PLS invocation. This is not a raw IO escape hatch: the request carries the scheduler-created, identity-keyed data views and the provider is solely responsible for resolving them to rows and targets.