Streaming table fields in Reltio Data Sharing with Databricks

Learn more about the fields available in Reltio Data Sharing with Databricks streaming tables.

Databricks streaming-table data shares provide type-specific tables for entities, relations, and interactions, and fixed-name streaming tables for matches, merges, links, workflows, and activities.

Entity fields

Reltio writes entity records to a streaming table named entity_{entityType}.

In a hierarchical schema, attributes stores the entity attributes in a single STRUCT. In a simplified schema, Reltio replaces the attributes structure with separate fields based on the attributes defined in your entity model.

The entity streaming tables contain the following fields:


Field	Data type	Description
`objectType`	`STRING`	Type of Reltio object represented by the record.
`id`	`STRING`	Unique identifier for the entity.
`uri`	`STRING`	Unique URI for the entity.
`version`	`BIGINT`	Version of the entity.
`timestamp`	`BIGINT`	Time when Reltio recorded the entity event.
`type`	`STRING`	Entity type defined in your tenant business model.
`attributes`	`STRUCT`	Entity attributes in a hierarchical schema.
`crosswalks`	`ARRAY<STRUCT>`	Source records associated with the entity.
`analyticsAttributes`	`STRING`	Analytical attributes associated with the entity.
`createdBy`	`STRING`	Identifier of the user who created the entity.
`createdTime`	`BIGINT`	Time when the source system created the entity.
`updatedBy`	`STRING`	Identifier of the user who last updated the entity.
`updatedTime`	`BIGINT`	Time when the source system last updated the entity.
`commitTime`	`BIGINT`	Time when the entity version was committed in Reltio.
`deleted`	`BOOLEAN`	Indicates whether the entity is deleted. Always `false` because deleted entities are not included.
`label`	`STRING`	Display label that Reltio generates from the configured label pattern.
`linked`	`BOOLEAN`	Indicates whether the entity is linked to another object.
`secondaryLabel`	`STRING`	Additional display label that Reltio generates from the configured secondary label pattern.
`tags`	`ARRAY`	Tags associated with the entity.
`startDate`	`BIGINT`	Date and time from which Reltio considers the entity active. Before this time, the entity is inactive. If `null`, no date is specified for the active period to begin.
`endDate`	`BIGINT`	Date and time through which Reltio considers the entity active. After this time, the entity is inactive. If `null`, no date is specified for the active period to end.
`ingestTime`	`TIMESTAMP`	Time when Databricks ingested the entity record from staging storage into the entity table.
`insertedTime`	`BIGINT`	Time when the record was written to staging storage. Available only in simplified schema.
`eventTime`	`BIGINT`	Time when the entity event occurred. Available only in simplified schema.
`deletedTime`	`BIGINT`	Always `null` because deleted entities are not included. Available only in simplified schema.

Relation fields

Reltio writes relation records to a streaming table named relation_{relationshipType}.

In a hierarchical schema, attributes contains the relation attributes as a STRUCT. In a simplified schema, fields derived from the relation model replace attributes.

The relation streaming tables contain the following fields:


Field	Data type	Description
`objectType`	`STRING`	Type of Reltio object represented by the record.
`id`	`STRING`	Unique identifier for the relation.
`uri`	`STRING`	Unique URI for the relation.
`type`	`STRING`	Relation type defined in your tenant business model.
`attributes`	`STRUCT`	Relation attributes in a hierarchical schema.
`commitTime`	`BIGINT`	Time when the relation version was committed in Reltio.
`createdBy`	`STRING`	Identifier of the user who created the relation.
`createdTime`	`BIGINT`	Time when the source system created the relation.
`crosswalks`	`ARRAY<STRUCT>`	Source records associated with the relation.
`deleted`	`BOOLEAN`	Indicates whether the relation is deleted. Always `false` because deleted relations are not included.
`linked`	`BOOLEAN`	Indicates whether the relation is linked to another object.
`timestamp`	`BIGINT`	Time when Reltio recorded the relation event.
`updatedBy`	`STRING`	Identifier of the user who last updated the relation.
`updatedTime`	`BIGINT`	Time when the source system last updated the relation.
`version`	`BIGINT`	Version of the relation.
`startObject`	`STRUCT`	Entity assigned to the start of the relationship. Includes the entity URI and crosswalks.
`endObject`	`STRUCT`	Entity assigned to the end of the relationship. Includes the entity URI and crosswalks.
`startRefIgnored`	`BOOLEAN`	Indicates whether the start-object reference is ignored.
`startRefPinned`	`BOOLEAN`	Indicates whether the start-object reference is pinned.
`endRefIgnored`	`BOOLEAN`	Indicates whether the end-object reference is ignored.
`endRefPinned`	`BOOLEAN`	Indicates whether the end-object reference is pinned.
`startDate`	`BIGINT`	Date and time from which the relation connects its start and end objects. Before this time, the relation is inactive. If `null`, no date is specified for the active period to begin.
`endDate`	`BIGINT`	Date and time through which the relation connects its start and end objects. After this time, the relation is inactive. If `null`, no date is specified for the active period to end.
`ingestTime`	`TIMESTAMP`	Time when Databricks ingested the relation record from staging storage into the relation table.
`insertedTime`	`BIGINT`	Time when the record was written to staging storage. Available only in simplified schema.
`eventTime`	`BIGINT`	Time when the relation event occurred. Available only in simplified schema.
`deletedTime`	`BIGINT`	Always `null` because deleted relations are not included. Available only in simplified schema.

Interaction fields

Reltio writes interaction records to a streaming table named interaction_{interactionType}.

In a hierarchical schema, attributes contains the interaction attributes as a STRUCT. In a simplified schema, fields derived from the interaction model replace attributes.

The interaction streaming tables contain the following fields:


Field	Data type	Description
`objectType`	`STRING`	Type of Reltio object represented by the record.
`id`	`STRING`	Unique identifier for the interaction.
`linked`	`BOOLEAN`	Indicates whether the interaction was replaced as part of an entity or relation merge.
`uri`	`STRING`	Unique URI for the interaction.
`version`	`BIGINT`	Version of the interaction.
`timestamp`	`BIGINT`	Time when Reltio recorded the interaction event.
`type`	`STRING`	Interaction type defined in your tenant business model.
`deleted`	`BOOLEAN`	Indicates whether the interaction is deleted. Always `false` because deleted interactions are not included.
`attributes`	`STRUCT`	Interaction attributes in a hierarchical schema.
`crosswalks`	`ARRAY<STRUCT>`	Source records associated with the interaction.
`members`	`MAP<STRING, STRUCT>`	Interaction roles and the entities assigned to each role.
`createdBy`	`STRING`	Identifier of the user who created the interaction.
`createdTime`	`BIGINT`	Time when the source system created the interaction.
`updatedBy`	`STRING`	Identifier of the user who last updated the interaction.
`updatedTime`	`BIGINT`	Time when the source system last updated the interaction.
`commitTime`	`BIGINT`	Time when the interaction version was committed in Reltio.
`ingestTime`	`TIMESTAMP`	Time when Databricks ingested the interaction record from staging storage into the interaction table.
`insertedTime`	`BIGINT`	Time when the record was written to staging storage. Available only in simplified schema.
`eventTime`	`BIGINT`	Time when the interaction event occurred. Available only in simplified schema.
`deletedTime`	`BIGINT`	Always`null`because deleted interactions are not included. Available only in simplified schema.

Match fields

Reltio writes match records to the matches streaming table.

The match streaming tables contain the following fields:


Field	Data type	Description
`objectType`	`STRING`	Type of Reltio object represented by the record.
`insertedTime`	`BIGINT`	Time when the match record was written to staging storage.
`entityId`	`STRING`	Identifier of the entity for which match information is recorded.
`manual_matches`	`ARRAY<STRUCT>`	Entity identifiers manually confirmed as matches to `entityId`.
`not_matches`	`ARRAY<STRUCT>`	Entity identifiers marked as not matching `entityId`.
`potential_matches`	`ARRAY<STRUCT>`	Entities identified as possible matches to `entityId`, including the applicable match rules and match score.
`version`	`BIGINT`	Version of the match record.
`deleted`	`BOOLEAN`	Indicates whether the match record is deleted. Always `false` because deleted match records are not included.
`timestamp`	`BIGINT`	Time when Reltio recorded the match event.
`ingestTime`	`TIMESTAMP`	Time when Databricks ingested the match record from staging storage into the matches table.

Merge fields

Reltio writes merge records to the merges streaming table.

The merge streaming tables contain the following fields.


Field	Data type	Description
`objectType`	`STRING`	Type of Reltio object represented by the record.
`directWinner`	`STRING`	Identifier of the object that directly won the merge.
`insertedTime`	`BIGINT`	Time when the merge record was written to staging storage.
`winnerId`	`STRING`	Identifier of the entity that remains after the merge.
`loserId`	`STRING`	Identifier of the entity merged into the winning entity.
`mergeKey`	`STRING`	Identifier used to track the merge. The value matches `loserId`.
`type`	`STRING`	Method used to merge the entities: `MANUAL`, `AUTO`, `ON_THE_FLY`, or `GROUP_MERGE`.
`deleted`	`BOOLEAN`	Indicates whether the merge record is deleted. Always `false` because deleted merge records are not included.
`mergeRulesUris`	`ARRAY`	URIs of the merge rules applied to the entities.
`matchRules`	`ARRAY`	Labels of the match rules that identified the entities as matches before the merge.
`version`	`BIGINT`	Version of the merge record.
`timestamp`	`BIGINT`	Time when Reltio recorded the merge event.
`ingestTime`	`TIMESTAMP`	Time when Databricks ingested the match record from staging storage into the matches table.

Link fields

Reltio writes link records tothe links streaming table.

The link streaming tables contain the following fields.


Field	Data type	Description
`objectType`	`STRING`	Type of Reltio object represented by the record.
`insertedTime`	`BIGINT`	Time when the link record was written to staging storage.
`winnerId`	`STRING`	Identifier of the entity that remains after the merge.
`loserId`	`STRING`	Identifier of the merged entity that links to the winning entity.
`deleted`	`BOOLEAN`	Indicates whether the link record is deleted. Always `false` because deleted link records are not included.
`version`	`BIGINT`	Version of the link record.
`timestamp`	`BIGINT`	Time when Reltio recorded the link event.
`ingestTime`	`TIMESTAMP`	Time when Databricks ingested the link record from staging storage into the links table.

Workflow fields

Reltio writes workflow records to the workflows streaming table.

The workflow streaming tables contain the following fields.


Field	Data type	Description
`objectType`	`STRING`	Type of Reltio object represented by the record.
`uri`	`STRING`	Unique URI for the workflow record.
`timestamp`	`BIGINT`	Time when Reltio recorded the workflow event.
`environmentName`	`STRING`	Reltio environment in which the workflow activity occurred.
`tenantId`	`STRING`	Identifier of the Reltio tenant in which the workflow activity occurred.
`objectURIs`	`STRING`	URIs of the Reltio objects associated with the workflow, such as entities or relations.
`resourceURIs`	`STRING`	URIs of the resources associated with the workflow.
`processInstanceId`	`STRING`	Unique identifier for an execution of the workflow process.
`taskId`	`STRING`	Unique identifier for the task within the process instance.
`processType`	`STRING`	Type of workflow process being executed.
`taskType`	`STRING`	Type of task defined in the workflow process.
`processInstanceCreateTime`	`BIGINT`	Time when the workflow process instance was created.
`taskCreateTime`	`BIGINT`	Time when the workflow task was created.
`username`	`STRING`	Identifier of the user associated with the workflow activity.
`assignee`	`STRING`	Identifier of the user assigned to the workflow task.
`processInstanceDueDate`	`BIGINT`	Date and time when the workflow process instance is due.
`decision`	`STRING`	Decision submitted for the workflow task, such as approve or reject.
`userActivityTime`	`BIGINT`	Time when the user performed the workflow action.
`processInstanceComplete`	`BOOLEAN`	Indicates whether the workflow process instance is complete.
`processInstanceCompletionTime`	`BIGINT`	Time when the workflow process instance completed.
`processSuspended`	`BOOLEAN`	Indicates whether the workflow process instance is suspended.
`comment`	`STRING`	Comment entered for the workflow activity.
`ingestTime`	`TIMESTAMP`	Time when Databricks ingested the workflow record from staging storage into the workflows table.

Activity fields

The activities streaming table stores metadata from the Reltio activity log.

The activity streaming table contains the following fields.


Field	Data type	Description
`objectType`	`STRING`	Type of Reltio object represented by the record.
`activityClientType`	`STRING`	Type of client that submitted the request, such as the Reltio UI or API. If the `globalId` header does not specify a client type, the value is `UNKNOWN`.
`activityId`	`STRING`	Unique identifier for the activity log record.
`activityMethod`	`STRING`	HTTP method used in the request.
`activitySource`	`STRING`	Source recorded for the activity.
`activityTimestamp`	`BIGINT`	Time when the activity occurred.
`activityUrl`	`STRING`	URL of the REST API request associated with the activity.
`activityUser`	`STRING`	Identifier of the user who performed the activity.
`activityDescription`	`STRING`	Detailed description of the activity.
`activityLabel`	`STRING`	Short label describing the activity, such as `USERSEARCH`, `USERPROFILEVIEW`, or `USERLOGIN`.
`items`	`ARRAY<STRUCT>`	Objects affected by the activity and details of the action performed on each object.
`ingestTime`	`TIMESTAMP`	Time when Databricks ingested the activity record from staging storage into the activities table.

Unify and manage your data