--- title: "Attach/Detach pipelines" slug: "dataset-pipeline-operations" updated: 2025-09-25T05:11:47Z published: 2025-09-25T05:11:47Z canonical: "docs.akridata.ai/dataset-pipeline-operations" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.akridata.ai/llms.txt > Use this file to discover all available pages before exploring further. # Pipeline operations on a dataset As described in the [Register dataset](/data-explorer/docs/register-dataset) article, you can attach pipelines to the dataset when the dataset is created. This article describes the steps to attach and detach pipelines after the dataset is successfully registered. ## Access Pipeline Operations 1. On the dataset main page, click the dataset card for which you want to perform the pipeline operations. ![](https://cdn.document360.io/3e9d4528-fbc6-4948-a804-8ee7068e7ac3/Images/Documentation/car_damage_dataset(1).jpg) 2. On the page for the selected dataset page, click the 3-dots icon adjacent to the **Catalog** button, to open the drop-down. ![](https://cdn.document360.io/3e9d4528-fbc6-4948-a804-8ee7068e7ac3/Images/Documentation/3-dots-icon.jpg) 3. Select **Pipelines**. Using this menu option, you can execute existing pipelines, attach a new pipeline to the dataset, or detach an existing pipeline from the dataset. ![](https://cdn.document360.io/3e9d4528-fbc6-4948-a804-8ee7068e7ac3/Images/Documentation/pipeline-operations.jpg) ## Execute Pipelines This option enables you to ingest the selected pipeline into the dataset. 1. On the dataset main page, click the 3-dots icon, select **Pipeline** > **Execute pipelines**. ![](https://cdn.document360.io/3e9d4528-fbc6-4948-a804-8ee7068e7ac3/Images/Documentation/pipeline-operations(1).jpg) The Ingest Now window opens displaying the Base URL of the pipeline. This field is not editable. 2. Enter the subdirectory path. You can leave this field blank to ingest all data, provide path to the subfolder from where the data should be ingested. ![](https://cdn.document360.io/3e9d4528-fbc6-4948-a804-8ee7068e7ac3/Images/Documentation/ingest-pipeline-now.jpg) 3. Select the maximum number of files that should be ingested. 4. Click **Ingest**. The application initiates the process of ingestion. ## Attach Pipeline 1. Select **Pipeline** > **Attach pipelines**. ![](https://cdn.document360.io/3e9d4528-fbc6-4948-a804-8ee7068e7ac3/Images/Documentation/attach-pipeline.jpg) 2. In the **Attach Pipeline** screen, select the pipeline from the drop-down of available pipelines. The 'starred' pipelines are the recommended pipelines. ![](https://cdn.document360.io/3e9d4528-fbc6-4948-a804-8ee7068e7ac3/Images/Documentation/select-pipeline-to-attach.jpg) 3. Select the policy for this attachment that determines the mode(scheduled Vs triggered) of ingestion and the compute resources where ingestion will be done. 1. Schedule policy(BETA): The ingestion will be triggered as per the provided schedule on the selected cluster. Currently, only one pre-provisioned cluster, 'AkridataEdgeCluster', is available for selection, and this list will be extended with user-registered clusters in the future. The schedule is specified using a [cron](https://crontab.guru/) string. 2. On-demand policy(BETA): In this mode, the ingestion is triggered by the user as needed on the selected cluster. 3. Manual adectl run: In this mode, the compute resource for ingestion is to be provisioned by the user and ingestion must be triggered using the adectl command line utility. ![](https://cdn.document360.io/3e9d4528-fbc6-4948-a804-8ee7068e7ac3/Images/Documentation/attach-pipelines-details.jpg) 4. Click the **Attach** button. ### View pipeline attachment details The list of attachments for a dataset can be viewed on the dataset details page. - Click the dataset card to open the dataset page. ![](https://cdn.document360.io/3e9d4528-fbc6-4948-a804-8ee7068e7ac3/Images/Documentation/car-damage-dataset.jpg) - On the dataset page, click the **PIPELINE** tab. This displays a list of all pipelines attached to the dataset, the featurizer type and the corresponding policy attached to the pipeline. ![](https://cdn.document360.io/3e9d4528-fbc6-4948-a804-8ee7068e7ac3/Images/Documentation/car-damage-pipelines.jpg) ### Operations on pipeline attachments Under the **Actions** column, you can perform the following: 1. For Schedule and On-demand policy attachments, click the View Details arrowhead as shown below to view details of the last executed ingestion session that was scheduled or triggered by the user. The details section shows the progress percent (for in-progress sessions) and other details.![](https://cdn.document360.io/3e9d4528-fbc6-4948-a804-8ee7068e7ac3/Images/Documentation/pipeline-ingestion-progress.jpg) 2. Click **Catalog** to view the catalog for the pipeline. 3. For Schedule and On-demand policy attachments, click **Ingest** to execute the pipeline as per the base URL. You can select the sub-directory and maximum number of files for ingestion. 4. Click the 3-dots icon to perform the following: ![](https://cdn.document360.io/3e9d4528-fbc6-4948-a804-8ee7068e7ac3/Images/Documentation/pipeline-actions.jpg) 1. **Detach** the pipeline. ![](https://cdn.document360.io/3e9d4528-fbc6-4948-a804-8ee7068e7ac3/Images/Documentation/confirm-detach-pipeline.jpg) 2. **Edit** the policy attached to the pipeline. ![](https://cdn.document360.io/3e9d4528-fbc6-4948-a804-8ee7068e7ac3/Images/Documentation/edit-pipeline-attachment.jpg) ## Detach Pipeline 1. Select **Pipeline >** **Detach Pipeline**. ![](https://cdn.document360.io/3e9d4528-fbc6-4948-a804-8ee7068e7ac3/Images/Documentation/detach-pipeline(2).jpg) 2. Select the pipeline to detach from the drop-down list of attached pipelines. ![](https://cdn.document360.io/3e9d4528-fbc6-4948-a804-8ee7068e7ac3/Images/Documentation/Screenshot%20from%202023-06-01%2018-35-30.png) 3. Click the **Detach** button. Ingested data stays after the 'Detach' operation Any data ingested by the detached pipeline will remain in the system and be accessible for catalog browsing and job creation. The detached pipeline will not be executed on new data. If the same pipeline is reattached, all data that entered the dataset while the pipeline was detached will be processed through the reattached pipeline.