# Objects configuration

These configuration items define how Caplin Transformer deals with objects.

A Transformer object is a piece of data that Transformer manages on behalf of client applications; for example, a financial instrument such as a [DataSource record](../datasource/datasource-records.md) containing a currency pair. Transformer object types include all the [DataSource data types](../datasource/datasource-data-types.md).

## contrib-return

**❗ IMPORTANT**\
Deprecated from Transformer 7.1.0. Use the [`contrib`](../datasource/datasource-data-services-configuration.md#contrib) option of [`add-source-group`](../datasource/datasource-data-services-configuration.md#add-source-group) instead.

`contrib-return` specifies when `TRUE` that if Transformer receives a [contribution](../liberator/liberator-client-publication.md) (updated data for a [subject](../datasource/datasource-subjects-symbols-and-fields.md)), it sends the contribution on to the [DataSource application](../datasource/index.md) (typically an [Integration Adapter](../platform-architecture/putting-data-into-the-platform.md)) that owns the subject of the contribution.

**Syntax:** `contrib-return <boolean>`

**Type:** boolean

**Default value:** `FALSE` (a contribution received by Transformer isn’t sent on to the DataSource application that owns the subject of the contribution)

## default-object-status-stale

`default-object-status-stale` specifies when `TRUE` that the default [status](../datasource/datasource-subject-status.md) of all objects is "stale".

**Syntax:** `default-object-status-stale <boolean>`

**Type:** boolean

**Default value:** `FALSE` (The default status of all objects is "ok")

Also see [`map-limited-status-to-ok`](transformer-peer-management-configuration.md#map-limited-status-to-ok) in [Peer management configuration](transformer-peer-management-configuration.md).

## record-max-cache

`record-max-cache` specifies the maximum number of updates to keep for each record containing [type 3 (historic) data](../datasource/datasource-type-3-data.md).

(This configuration item is equivalent to the Liberator configuration item [`record-type3-history-size`](../liberator/liberator-object-configuration-part-2.md#record-type3-history-size))

**Syntax:** `record-max-cache <maximum-number-of-updates>`

**Type:** integer

**Default value:** `10` updates

## type2-hash-size

`type2-hash-size` specifies the size in table entries of the Transformer hashtable that’s used to access cached [Type 2 data](../datasource/datasource-type-2-data.md).

(This configuration item is equivalent to the Liberator configuration item [`record-type2-hash-size`](../liberator/liberator-object-configuration-part-2.md#record-type2-hash-size))

**Syntax:** `record-type2-hash-size <hashtable-size-in-entries>`

**Type:** integer

**Default value:** `65536` entries

---

**See also:**

* Reference: [Memory and cache configuration](transformer-memory-and-cache-configuration.md)
* Reference: [Peer Management configuration](transformer-peer-management-configuration.md)