Trigger an adhoc operation on a dataset

POST 
/datasets/:id

Triggers an adhoc background operation on a dataset. The caller must have at least editor access on the dataset. Supported actions (via the action query parameter):

• run_data_profiling_job — Triggers an AWS Glue data profiling job for the dataset via the EventRules lambda. Optionally accepts NumberOfWorkers and Timeout in the request body to override defaults. Returns immediately with a confirmation message; the job runs asynchronously.

• run_bda_extraction — Triggers a Bedrock Data Automation (BDA) extraction job for the dataset. Requires editor access, S3 (object storage) TargetLocation, IsBDAExtractionEnabled=true, Datasets AI enabled in the environment, a BDA-supported region, and a supported file type. Optionally accepts FileProcessingMode, FileIds, FromTime, ToTime, TargetDatasetId, and TargetDatasetProvided in the request body. Returns immediately; the job runs asynchronously.

• run_eda_profiling — Triggers data profiling for the dataset. Supported only for internal s3athena or redshift datasets that are not Hudi or Iceberg. If profiling is already complete, returns the current status unless force=true is passed to regenerate. Rejects the call if profiling is already in progress.

Request

Responses

200

Operation triggered successfully or already completed

Response Headers

Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers

400

Invalid input or ineligible dataset

Response Headers

Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers

403

User does not have editor access on the dataset

Response Headers

Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers

500

Internal failure during operation trigger

Response Headers

Access-Control-Allow-Origin
Access-Control-Allow-Methods
Access-Control-Allow-Headers