create-datahub-dataset
dci create-datahub-dataset
Creates a new DataHub dataset. A dataset is a logical grouping of events that share the same provider name. Creating a dataset allows you to define metadata such as name and description before ingesting events.
Request
Content-Type: application/json
Schema
{
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "The name of the dataset. Allowed characters: alphanumeric (0-9,a-z,A-Z), underscore (_), dash (-), and spaces between words.",
"example": "My Custom Dataset",
"pattern": "^[a-zA-Z0-9_-]+( [a-zA-Z0-9_-]+)*$"
},
"description": {
"type": "string",
"description": "An optional description for the dataset.",
"example": "Dataset for tracking custom business metrics"
}
}
}
Output
Created - Dataset created successfully.
By default dci renders the result as a table. Use --output json to get the full structure described below — see Output formats.
| Field | Type | Description |
|---|---|---|
name | string | The name of the dataset. |
description | string | The description of the dataset. |
records | integer (int64) | The number of records in the dataset. |
updatedBy | string | The email of the user who last updated the dataset. |
lastUpdated | string | The timestamp of the last update. |
Raw JSON schema
{
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "The name of the dataset.",
"example": "My Custom Dataset"
},
"description": {
"type": "string",
"description": "The description of the dataset.",
"example": "Dataset for tracking custom business metrics"
},
"records": {
"type": "integer",
"format": "int64",
"description": "The number of records in the dataset.",
"example": null,
"nullable": true
},
"updatedBy": {
"type": "string",
"description": "The email of the user who last updated the dataset.",
},
"lastUpdated": {
"type": "string",
"description": "The timestamp of the last update.",
"example": "2024-03-10T23:00:00Z"
}
}
}
Errors
On failure, dci prints a single error message — with a hint when one is available — and exits with a typed code your scripts can branch on. See Errors and exit codes for the full contract.
| HTTP status | Exit code | Error code | Meaning |
|---|---|---|---|
| 400 | 30 | VALIDATION_ERROR | The arguments or request body were rejected. Review the command's flags and payload. |
| 401 | 10 | AUTHENTICATION_FAILED | Not signed in, or the API token is invalid. Run dci login or check DCI_API_KEY. |
| 403 | 11 | PERMISSION_DENIED | The DoiT user or the active customer context does not have access. |
| 500 | 40 | API_SERVER_ERROR | The API failed to process the request. Retryable; contact DoiT support if it persists. |
Aliases: createdatahubdataset