Unify and manage your data

Tenant Configuration Parameters Reference

Learn about the configurable parameters available at the tenant level in Reltio and how they influence storage, search, relations, streaming, and operational behavior.

Tenant-level configuration parameters define how Reltio manages data storage, search indexing, relations, crosswalks, streaming, lifecycle actions, and logging for a tenant. This topic summarizes the configurable parameters from the Tenant Storage Management API that can be safely exposed in public documentation.

Use this topic as a high-level reference and consult the linked configuration and API topics at the end of each section for implementation details and examples.

Administrative and General Tenant Properties

These parameters identify the tenant and control general operational behavior.

ParameterDescriptionTypeDefault
tenantIdUnique identifier of the tenant.StringRequired
tenantNameHuman-readable name of the tenant; defaults to tenantId if omitted.StringNone
customerNameName of the customer organization associated with the tenant.StringNone
ownerEmailsList of tenant owner email addresses notified about configuration actions.ArrayNone
maxRequestsPerClusterMaximum number of concurrent requests processed per cluster for this tenant.IntegerUnlimited
maxPeriodicTasksPerTenantMaximum number of periodic tasks allowed to run for the tenant.IntegerNone
immutableRefAttrsByDefaultSpecifies whether reference attributes are treated as immutable unless explicitly configured otherwise.Booleanfalse
useActivityLogInTasksEnables use of the activity log as a data source for tasks and processing.Booleanfalse

For more information about tenant-level setup, see Tenant Configuration at a glance.

Storage and History Configuration

These parameters influence database storage behavior, history handling, and object limits for the tenant.

ParameterDescriptionTypeDefault
dataStorageConfigDefines primary data storage configuration for the tenant.JSONRequired
historyDataStorageModeControls whether history data is stored in normal or compact mode.Stringstandard
interactionTtlTime-to-live for interactions, after which they may be purged from storage.IntegerNone
eventsSizeLimitMaximum serialized size of event messages published for the tenant.LongUnlimited
maxChangedObjectsMaximum number of entity changed events generated from a single operation.Integer-1 (unlimited)
updateAttributesEntitiesBatchSizeNumber of entities processed per batch for attribute updates.IntegerNone
interactionTtlConfigures retention period of interaction objects before deletion.IntegerNone

For details on storage options, see Configuration API.

Search and Index Configuration

These parameters control search index structure, performance tuning, and indexing behavior.

ParameterDescriptionTypeDefault
searchStorageConfigurationDefines configuration of search indices, shards, and replicas.JSONRequired
waitForAllShardsWaits for all shards to be available before returning index operations.Booleantrue
prefixSearchMaxExpansionsMaximum term expansions allowed for prefix searches.Integer50
maxAttributeLengthMaximum length of attribute text stored in the search index.IntegerNone
preserveCursorPreserves search cursor between paginated requests.Booleanfalse
indexRDMLookupsEnables indexing of RDM lookups for search.Booleanfalse
indexOnlySearchableAttributesIndexes only attributes marked as searchable.Booleanfalse
indexOvStrategyDefines strategy for indexing operational values versus all values.StringOV_ONLY
indexMLRulesIncludes machine learning rules in the index where applicable.Booleanfalse
indexActivityDeltaEnables indexing of activity delta information.Booleanfalse
indexRefreshIntervalFrequency at which the index is refreshed.String1s
useSingleIndexUses a single shared index for all entity types.Booleanfalse
refreshIndexOnInsertsRefreshes the index immediately after insert operations.Booleanfalse
maxNumberOfResultsMaximum number of search results returned in a single query.Integer10000
numberOfShardsNumber of primary shards for main search indices.Integer5
numberOfRelationsShardsNumber of shards for relation indices.Integer5
numberOfInteractionsShardsNumber of shards for interaction indices.Integer5
numberOfActivitiesShardsNumber of shards for activity indices.Integer5
indexingErrorsMonitoringEnables monitoring and tracking of indexing errors.Booleanfalse
prepareRelationIndexConfigures whether relation data is prepared specifically for indexing.Booleantrue
indexRelationsEnables indexing of relations for search and reporting.Booleantrue
maxSearchFileLinesMaximum number of lines allowed in search export files.Integer1000000
defaultBoostFactorDefault relevance boost factor applied to indexed fields.Float1.0
indexRequestTimeoutMaximum time allowed for index requests before timeout.Integer60000
indexExportCsvHeadersControls whether CSV downloads include header rows.Booleantrue
appendEqualsAnalyzedForContainsWordStartingWithTunes analyzers for contains-word-starting-with and equals queries.Booleanfalse
proximateGeoTokenVersionVersion of the geo tokenization algorithm used for proximity searches.Integer1

For information on search behavior and tuning, see Search API.

Matching, Grouping, and OV Behavior

These parameters control matching behavior, grouping logic, and operational value (OV) calculation.

ParameterDescriptionTypeDefault
collapseNonOvNestedsWhenMatchOvOnlyEnabledCollapses non-OV nested values when matchOvOnly is enabled for attributes.Booleanfalse
dropOvBeforeAndAfterLcaForNonDefaultGroupsDrops OV calculation before and after lifecycle actions for non-default groups.Booleanfalse
suppressRelevanceInMatchOutputOmits relevance scores from match output responses.Booleanfalse
doNotTakeRequiredFromSubnestedPrevents required constraint propagation from sub-nested attributes.Booleanfalse
groupingConfigDefines grouping behavior and grouping rules for entities.JSONNone
enabledTurns the grouping functionality on or off for the tenant.Booleanfalse
ovCalculationVersionSelects the algorithm version for OV calculation.Integer1

For matching and survivorship configuration, see Configuring Survivorship Rules in the L3 .

Reference, Crosswalk, and RDM Configuration

These parameters control how references, crosswalks, and lookup values behave across entities.

ParameterDescriptionTypeDefault
resolveLoserStartEndObjectsInRelationsReassigns relations to winner entities when start/end entities are merged.Booleanfalse
sortCrosswalksInLUDNonAdvancedSorts crosswalks in last updated date order for non-advanced flows.Booleanfalse
updateRawValueToCanonicalCodeUpdates raw attribute values to canonical lookup codes.Booleanfalse
readEntitiesInAutoMergeHandlerAsInMergeByCrosswalksReads entities during auto-merge using merge-by-crosswalks semantics.Booleanfalse
useRawValueAsDefaultForCleanseUses the raw value as default when cleanse does not return a result.Booleanfalse
enableCleanseCrosswalkLogLogs crosswalk changes resulting from cleansing operations.Booleanfalse
changeCleanseCrosswalkUpdateDateUpdates crosswalk update dates when cleanse changes values.Booleanfalse
cleanse.chain.resolvelookupEnables resolve-lookup step within the cleanse chain.Booleanfalse
populateSingleAttributeUpdateDatesInRefCrosswalkPopulates update dates for single attributes in reference crosswalks.Booleanfalse
excludeMergeCrosswalksFromMergeTreeExcludes merge crosswalks when building merge tree.Booleanfalse
skipEndDatedReferenceAttributesSkips end-dated reference attributes in specific API responses.Booleanfalse
ignoreNonOVChangesWhenUpdateThroughReferencedEntitySuppresses events when only non-OV values change in referenced entities.Booleanfalse
useOnlyOvValuesInReferencedEntitiesRestricts referenced entities to OV values so non-OV changes do not propagate.Booleanfalse
permanentLookupsStoreConfigures use of permanent storage for lookup values.Booleanfalse
transcodeByEndDatedCrosswalksAllows lookup transcoding using end-dated crosswalks.Booleanfalse
includeDisabledLookupsIncludes disabled lookup values during transcoding.Booleanfalse
multiParentTranscodingEnables transcoding where a lookup can have multiple parent values.Booleanfalse
publishRDMErrorsPublishes RDM-related errors to logs or monitoring.Booleanfalse
cacheControls whether RDM lookup data is cached.Booleantrue
cachedIndicates if the RDM tenant configuration is cached.Booleantrue
rdmTenantsDefines the list or mapping of RDM tenants used by this tenant.ArrayNone
oauthInstanceOAuth instance identifier used for RDM integration.StringNone
serviceUriService endpoint URI for RDM or external lookup services.StringNone
loqateDefaultCountryDefault country code used when cleansing addresses with Loqate.StringUSA
Verification status mappingMaps Loqate verification statuses to tenant-specific statuses.JSONNone
Address cleanser processDefines which address cleanse process (for example, CASS or SERP) is used.StringLicense-dependent
dataProtectionTaskTimeWaitThresholdMaximum number of days a data protection task waits before processing.Integer7
updateAttributeUpdateDatesOnActualChangesUpdates attribute updatedDate only when the underlying value changes.Booleantrue
alwaysFillStartEndObjectCrosswalksEnsures both start and end object crosswalks are always populated when creating relations.Booleanfalse
connectRelationsToDefaultCrosswalkUses the tenant's default crosswalk as start/end crosswalk when relations are created using URIs.Booleantrue

For lookup and RDM configuration, see RDM Lookups API and Set Cleanse Functions Configuration.

Streaming and Messaging Configuration

These parameters control event streaming, JMS publishing behavior, filters, and payload structure.

ParameterDescriptionTypeDefault
streamingEnabledEnables or disables event streaming for the tenant.Booleantrue
streamingAPIEnabledControls whether events from API operations are published to streaming destinations.Booleantrue
JMSEventsFilteringFieldsDefines entity fields included in JMS event payloads.ArrayNone
RelationEventsFilteringFieldsDefines relation fields included in JMS event payloads.ArrayNone
skipPayloadWhen true, sends metadata-only events without full payload body.Booleanfalse
analyzeOvChangesAnalyzes OV changes when determining whether to publish events.Booleanfalse
emptyStartEndRelationCrosswalksControls whether relation events may contain empty start/end crosswalks.Booleanfalse
largeObjectsSupportEnables support for publishing large objects in events.Booleanfalse
JMSEventsTimeToLiveTime-to-live for JMS events in the message broker.IntegerTBD
JMSIncludeMergeTimeIncludes merge time information in JMS event payloads.Booleanfalse
typeFilterFilters event publication by object type.StringNone
dtssQueueDefines the queue name used for DTSS-related streaming.StringNone
messagingGrouping object for messaging configuration parameters.JSONNone
messagingNameLogical name for the messaging configuration.StringNone
nameName of an individual messaging endpoint configuration.StringNone
typeType of messaging provider (for example, JMS or cloud queue).StringNone
providerProvider identifier for the messaging system.StringNone
JMSDestinationPrefixPrefix applied to JMS destination names.StringNone

For details on streaming configuration, see Configuration API.

Lifecycle and LCA Processing

These parameters control how lifecycle actions and hooks are invoked and how events are published around merges and saves.

ParameterDescriptionTypeDefault
earlyPublishEventsBeforeAfterSaveLCAHookPublishes events before afterSave or afterMerge lifecycle hooks are executed.Booleanfalse
triggerBeforeMergeLCAonManualOnlyTriggers beforeMerge and afterMerge lifecycle hooks only for manual merges.Booleanfalse
lifecycleActionsServiceSpecifies the service endpoint handling lifecycle actions.StringNone
dropOvBeforeAndAfterLcaForNonDefaultGroupsDisables OV recalculation before and after lifecycle actions for non-default groups.Booleanfalse

For lifecycle action configuration, see Life Cycle Actions (LCA) Service API.

Activity Log Configuration

These parameters configure storage, retention, and usage of the activity log.

ParameterDescriptionTypeDefault
activityLogConfigContainer for tenant-level activity log configuration.JSONNone
ttlRetention period for activity log records in primary storage.String4 months
longTermStorageParameters controlling long-term storage of activity logs in external systems (for example, GBQ).JSONDisabled
returnObjectLabelsInScanDetermines whether object labels are returned when scanning activity logs.Booleantrue
convertNullsToEmptyLabelsInCassandraReturns empty labels instead of null for unspecified labels in activity storage.Booleanfalse
useActivityLogInTasksEnables activity log usage as a data source for tasks.Booleanfalse
extendedLogMaxObjectsPerPostLimitExceededMaximum number of objects logged when post-limit-exceeded events occur.IntegerNone

For usage of the activity log, see Search using Activity Log API.

Export and Quotas Configuration

These parameters control export behavior, GBQ integration, quotas, and JSON compression.

ParameterDescriptionTypeDefault
exportConfigDefines tenant-level configuration for export operations.JSONNone
quotasLowWatermarkPercentPercentage threshold at which quota low-watermark alerts are generated.Integer80
quotasControlEnabledEnables enforcement of tenant quotas.Booleanfalse
compressJsonsCompresses JSON payloads for exports and storage where supported.Booleanfalse
gbqLimitBytesMaximum number of bytes allowed per GBQ export operation.LongNone
tableTarget table name used for GBQ or external export destinations.StringNone

For export options and quotas, see Export Service APIs.

Storage-Level Parameters

These parameters control tenant history, Bigtable usage, and storage behavior for specific storage backends.

ParameterDescriptionTypeDefault
historyGBTMigrationEnables dual-writing history to Google Bigtable during migration.Booleanfalse
historyBigTableConfigDefines the configuration for storing history in Google Bigtable.JSONNone
historyKeyspaceConfigSpecifies the keyspace configuration for primary history storage.JSONNone
historySecondaryKeyspaceConfigDefines secondary history keyspace configuration when dual storage is enabled.JSONNone
matchKeyspaceConfigConfiguration for the Cassandra keyspace used for match column families.JSONNone
interactionKeyspaceConfigKeyspace configuration for storing interaction objects.JSONNone

Optional and Miscellaneous Parameters

These parameters control optional behaviors and fine-tuning aspects for the tenant.

ParameterDescriptionTypeDefault
useNewDCRsEnables use of the new Data Change Request (DCR) model.Booleanfalse
useNewDCRsAsDefaultUses the new DCR model as the default for change management.Booleanfalse
repeatAllOperationsOnConflictRepeats operations when conflicts are detected during updates.Booleanfalse
allowRebuildInBackgroundAllows rebuild operations to run in the background.Booleanfalse
detailedTracingEnables detailed tracing logs for troubleshooting.Booleanfalse
disableUseHashForRecleanseDisables hash-based optimization for recleanse operations.Booleanfalse
fullySerializeStartEndCrosswalksSerializes full start and end crosswalk content for relation objects.Booleanfalse
allowSkipReferenceObjectsUpdatePrevents skipping ENTITY_CHANGED events for referenced entities when optimizations apply.Booleanfalse
allowSkipRefChecksSkips validation of reference object consistency when assembling business objects.Booleanfalse
overridePrevValueStatusAllows a new value to override pin or ignore status even when identical to the previous value.Booleanfalse

For optional configuration patterns, see Tenant Configuration at a glance.

Tenant Configuration Guidelines

Use these parameters with consideration for tenant size, data volume, and performance requirements. For large tenants, review shard counts, indexing settings, and event streaming limits with Reltio Support to avoid performance bottlenecks.

Always validate configuration changes in a non-production environment.