> For the complete documentation index, see [llms.txt](https://docs.rierino.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rierino.com/devops/batch-tasks.md).

# Batch Tasks

Python processes and processors allow execution of batch tasks such as import, export and ML training.

Python runners are used for executing batch processes, which are typically deployed as one-time jobs or scheduled cron-jobs. While it is possible to use Java runners and sagas for executing and scheduling any flow, these batch runners can be utilized for long running processes, as well as leveraging Python specific ML libraries without blocking real-time microservice resources. 

Two main types of runners are available out-of-box, using [Rierino Python Packages](/installation/artifacts.md):

## rierino\_util.Runner

Triggers "[Process](/devops/batch-tasks/python-processes.md)" type Python tasks, using a "base64" command line argument to pass base64 encoded contents of the Json object for process parameters. These parameters should include:

| Parameter | Definition                                | Example                                                                                               | Default |
| --------- | ----------------------------------------- | ----------------------------------------------------------------------------------------------------- | ------- |
| package   | Python package of the module to execute   | rierino\_runner                                                                                       | -       |
| module    | Process module to execute                 | IterateProcess                                                                                        | -       |
| args      | Process module specific arguments to pass | {"parameters": {"iterator":{ "module": "rierino\_runner.iterator.DataIterator", "element": "list" }}} | -       |

## rierino\_runner.ProcessorRunner

Triggers "[Processor](/devops/batch-tasks/python-processors.md)" type Python tasks, for single step, relatively simpler executions, using the following command line arguments:

| Argument            | Definition                                                                                                     | Example              | Default |
| ------------------- | -------------------------------------------------------------------------------------------------------------- | -------------------- | ------- |
| base64              | Base64 encoded contents of the Json object for full parameters (can include dict, package, module, parameters) | -                    | -       |
| dict                | Json string for passing input payload to processor                                                             | {list: \[]}          | -       |
| package             | Python package of the module to execute                                                                        | rierino\_runner      | -       |
| module              | Processor module to execute                                                                                    | RestProcessor        | -       |
| \[processor\_param] | Key=value pair for passing individual parameters to the processor                                              | {url: "example.com"} | -       |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rierino.com/devops/batch-tasks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.