Skip to main content
Version: Next

DataHubExecutionRequest

Technical Reference Guide

The sections above provide an overview of how to use this entity. The following sections provide detailed technical information about how metadata is stored and represented in DataHub.

Aspects are the individual pieces of metadata that can be attached to an entity. Each aspect contains specific information (like ownership, tags, or properties) and is stored as a separate record, allowing for flexible and incremental metadata updates.

Relationships show how this entity connects to other entities in the metadata graph. These connections are derived from the fields within each aspect and form the foundation of DataHub's knowledge graph.

Reading the Field Tables

Each aspect's field table includes an Annotations column that provides additional metadata about how fields are used:

  • ⚠️ Deprecated: This field is deprecated and may be removed in a future version. Check the description for the recommended alternative
  • Searchable: This field is indexed and can be searched in DataHub's search interface
  • Searchable (fieldname): When the field name in parentheses is shown, it indicates the field is indexed under a different name in the search index. For example, dashboardTool is indexed as tool
  • → RelationshipName: This field creates a relationship to another entity. The arrow indicates this field contains a reference (URN) to another entity, and the name indicates the type of relationship (e.g., → Contains, → OwnedBy)

Fields with complex types (like Edge, AuditStamp) link to their definitions in the Common Types section below.

Aspects

dataHubExecutionRequestInput

An request to execution some remote logic or action. TODO: Determine who is responsible for emitting execution request success or failure. Executor?

FieldTypeRequiredDescriptionAnnotations
taskstringThe name of the task to execute, for example RUN_INGEST
argsmapArguments provided to the task
executorIdstringAdvanced: specify a specific executor to route the request to. If none is provided, a "default" e...Searchable
sourceExecutionRequestSourceSource which created the execution request
requestedAtlongTime at which the execution request input was createdSearchable (requestTimeMs)
actorUrnstringUrn of the actor who created this execution request.Searchable

dataHubExecutionRequestSignal

An signal sent to a running execution request

FieldTypeRequiredDescriptionAnnotations
signalstringThe signal to issue, e.g. KILL
executorIdstringAdvanced: specify a specific executor to route the request to. If none is provided, a "default" e...
createdAtAuditStampAudit Stamp

dataHubExecutionRequestResult

The result of an execution request

FieldTypeRequiredDescriptionAnnotations
statusstringThe status of the execution requestSearchable (executionResultStatus)
reportstringThe pretty-printed execution report.
structuredReportStructuredExecutionReportA structured report if available.
startTimeMslongTime at which the request was createdSearchable
durationMslongDuration in milliseconds

Common Types

These types are used across multiple aspects in this entity.

AuditStamp

Data captured on a resource/association/sub-resource level giving insight into when that resource/association/sub-resource moved into a particular lifecycle stage, and who acted to move it into that specific lifecycle stage.

Fields:

  • time (long): When did the resource/association/sub-resource move into the specific lifecyc...
  • actor (string): The entity (e.g. a member URN) which will be credited for moving the resource...
  • impersonator (string?): The entity (e.g. a service URN) which performs the change on behalf of the Ac...
  • message (string?): Additional context around how DataHub was informed of the particular change. ...

Relationships

Outgoing

These are the relationships stored in this entity's aspects

  • ingestionSource

    • DataHubIngestionSource via dataHubExecutionRequestInput.source.ingestionSource

Global Metadata Model

Global Graph