> 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/microservices/building-blocks/additional-elements/global-settings.md).

# Global Settings

Global settings are typically used for runner specific configurations which are not specific to an element type, and can be loaded after the runner initialization.

Globals allow defining and loading properties which are not tied to a specific system component to runners (e.g. to application.properties files). Typical use cases include:

* **Serde Configurations:** Defining serialization/deserialization settings for different runner types, used across all streams (e.g. task.drop.serialization.errors setting for Samza runners).
* **Runner Specific Configurations:** Core Spring, Samza, etc. properties to apply (e.g. job.coordinator.system for Samza runners).

These settings are typically defined only once at the initial Rierino platform deployment (with predefined values) and do not change over time. The main benefit of these elements is to provide complete control over underlying system library settings.

For more details on available generic settings, please refer to your selected runner's own documentation (e.g. Spring, Samza).

Since they are runner specific, global settings usually have their runner type defined.

{% hint style="info" %}
An example is "task.ignored.exceptions" configuration for [Samza](https://samza.apache.org/learn/documentation/latest/jobs/configuration-table.html), which specifies list of exceptions to ignore in a task's process or window methods.
{% endhint %}


---

# 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/microservices/building-blocks/additional-elements/global-settings.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.
