package nitric.proto.batch.v1

Get desktop application:
View/edit binary Protocol Buffers messages

Service for submitting jobs to be processed

• rpc SubmitJob (JobSubmitRequest, JobSubmitResponse)

  batch.proto:21

  message JobSubmitRequest

  batch.proto:87

  • string job_name = 1

    The name of the job that should handle the data

  • optional JobData data = 2

    The data to be processed by the job

  message JobSubmitResponse

  batch.proto:95

  (message has no fields)

Service for processing jobs

• rpc HandleJob (stream ClientMessage, stream ServerMessage)

  batch.proto:16

  message ClientMessage

  batch.proto:24

  • string id = 1

    globally unique ID of the request/response pair

  • oneof content

    • RegistrationRequest registration_request = 2

      Register a handler for a job

    • JobResponse job_response = 3

      Handle a job submission

  message ServerMessage

  batch.proto:74

  ServerMessage is the message sent from the nitric server to the service

  • string id = 1

    globally unique ID of the request/response pair

  • oneof content

    • RegistrationResponse registration_response = 2

    • JobRequest job_request = 3

      Request to a job handler

Used in: JobRequest, JobSubmitRequest

• oneof data

  • google.protobuf.Struct struct = 1

Used in: ServerMessage

• string job_name = 1

• optional JobData data = 2

Used in: RegistrationRequest, deployments.v1.Job

• float cpus = 1

  The number of CPUs to allocate for the job

• int64 memory = 2

  The amount of memory to allocate for the job

• int64 gpus = 3

  The number of GPUs to allocate for the job

Used in: ClientMessage

• bool success = 1

  Mark if the job was successfully processed

Used in: ClientMessage

• string job_name = 1

• optional JobResourceRequirements requirements = 2

  Register with default requirements

Used in: ServerMessage

(message has no fields)