Application properties

Overview

These are the properties used to configure the mr-application module.

Module properties

Distributed deployment properties

The following properties are consumed by Spring EnvironmentPostProcessors that run before the application context starts. They are not bound via @ConfigurationProperties so they do not appear in the auto-generated table above.

Property	Default	Description
`mr.cluster.jgroups-bind-addr`	(unset)	Passed verbatim to JGroups as `jgroups.bind_addr`. Use a JGroups address expression such as `match-address:10.1..` to force cluster traffic onto the correct network interface when multiple interfaces are present (e.g. Docker bridge + VPC NIC on EC2). When unset the post-processor is a no-op; JGroups selects the interface automatically. Can be overridden by passing `-Djgroups.bind_addr=…` as a JVM argument.
`mr.cluster.jdbc-ping.connection-url`	(unset)	JDBC URL for the PostgreSQL database used by JGroups JDBC_PING for cluster member discovery (e.g. `jdbc:postgresql://host/db`). Alternative to the `JDBC_PING_DATABASE_CONNECTION_URL` PaaS environment variable. Requires `mr.messenger.protocol-file-path: jgroups-protocols/protocol-jdbc-ping.xml`.
`mr.cluster.jdbc-ping.connection-username`	(unset)	Database username for JDBC_PING discovery.
`mr.cluster.jdbc-ping.connection-password`	(unset)	Database password for JDBC_PING discovery. Stored as a JVM system property at startup (JGroups platform requirement); Spring Actuator `/env` masks this key by default.

Telemetry export properties

The mr.open-telemetry.* properties are bound through OpenTelemetryProperties and appear in the auto-generated table above. The otel.* keys below do not: they are standard OpenTelemetry SDK properties, read by the exporter wiring rather than bound. The switch that enables the export, mr.enable.tracing.open-telemetry (default false), is bound through FeatureProperties and documented in mr-common-config.

Property	Default	Description
`otel.exporter.otlp.protocol`	`http/protobuf`	OTLP transport. Set to `grpc` for OTLP gRPC, which changes the default endpoint to `http://localhost:4317`.
`otel.exporter.otlp.endpoint`	`http://localhost:4318`	Collector endpoint for spans, metrics and log records. Must match the protocol in use: an HTTP endpoint does not accept gRPC traffic, or the reverse.
`otel.exporter.otlp.headers`	(empty)	Comma-separated `key=value` headers added to every OTLP request, forwarded as-is. Cloud-hosted backends use this for authentication.
`otel.exporter.otlp.compression`	`none`	On-wire compression. Set to `gzip` to reduce egress bandwidth.
`otel.service.name`	(unset)	The `service.name` OTel resource attribute. When unset it resolves to `market-risk-accelerator`, or to `Atoti Server` if `mr.open-telemetry.legacy-mode` is `true`.

Headers and compression apply to both transports. The Micrometer OTLP metrics registry (management.otlp.metrics.export, HTTP only, disabled by default) is a separate export pipeline and is not affected by otel.exporter.otlp.protocol. For TLS, the exporter uses the JVM trust store rather than the otel.exporter.otlp.certificate family; see the Migration guide.

DirectQuery properties

The following properties are read by DirectQueryActivePivotConfig via @Value and are therefore not bound via @ConfigurationProperties. Each selects the vector layout of one store’s external table, and each is matched against VectorType case-insensitively. An unrecognized value fails startup with an IllegalArgumentException naming the property.

Property	Store	Default
`mr.directquery.tradepnl-vector-layout`	`TradePnLs`	(unset)
`mr.directquery.tradesensitivities-vector-layout`	`TradeSensitivities`	(unset)
`mr.directquery.marketshift-vector-layout`	`MarketShifts`	(unset)
`mr.directquery.sensiladder-vector-layout`	`SensiLadders`	(unset)

Leaving a property unset is the same as setting DEFAULT. Both resolve at runtime from the target database: NATIVE where the database stores vectors natively, ROW otherwise.

Value	Layout
`DEFAULT`	Resolved from the database, as above. Never resolves to `COLUMN`.
`ROW`	A separate vector table, one row per value with its index, concatenated back by Atoti.
`ROW_SAME_TABLE`	As `ROW`, but the vector rows stay in the original table and the scalar fields are duplicated along it, so no second table is created.
`COLUMN`	One column per vector index, named `<column>_0`, `<column>_1` and so on, up to 250 by default. The column base name differs per store: `PNL_VECTOR` on `TradePnLs`, `LADDER` on `TradeSensitivities`, `VALUES` on `MarketShifts`, `SCALE` on `SensiLadders`.
`NATIVE`	Vectors stored natively by the database. An additional translator may be needed.

These properties are applied only when DirectQueryActivePivotConfig builds the Migrator itself. An application that supplies its own Migrator bean overrides that step, and all four properties are then ignored with no warning and no startup failure.

​Overview

​Module properties

​Distributed deployment properties

​Telemetry export properties

​DirectQuery properties

Overview

Module properties

Distributed deployment properties

Telemetry export properties

DirectQuery properties