Package ai.pipestream.module.pipelineprobe.moduletest.engineperf

package ai.pipestream.module.pipelineprobe.moduletest.engineperf
  • Class
    Description
    IntakeDocStream
    One open bidi stream to connector-intake's uploadPipeDocStream — the SAME protocol the JDBC connector speaks (IntakeCrawlStream is the reference implementation): StreamContext handshake first (datasource + api key + crawl_id), then one PipeDocItem per doc with per-doc acks; backpressure is HTTP/2 native.
    IntakeDocStream.DocAck
    Per-doc intake outcome.
    ModuleEnginePerfSession
    Engine-path perf (Test 2): the sidecar acts as its OWN connector and pushes corpus docs through the production front door — connector-intake's uploadPipeDocStream — so the engine does everything it does for a real crawl: claim-check staging, fan-out to the subscribed graph, work dispensing over the bidi work stream, and the module's own worker loop self-ramps against the backlog.