Skip to main content

Delete Nexset

Deleting Nexsets in Nexla allows you to remove data processing workflows that are no longer needed, helping you maintain a clean and organized data processing infrastructure while freeing up resources for new workflows.

Nexset Deletion Overview​

Nexset deletion is a critical operation that permanently removes data processing workflows and their associated configurations, requiring careful consideration of dependencies and impact on your data processing pipeline.

Core Deletion Capabilities​

The deletion system provides several key capabilities for safely removing Nexsets from your infrastructure.

Safe Deletion​

Ensure safe removal of Nexsets:

  • Dependency Checking: Verify no dependent systems rely on the Nexset
  • Data Preservation: Preserve important data and configurations
  • Impact Assessment: Assess impact on data processing pipelines
  • Rollback Planning: Plan for potential rollback scenarios

Resource Cleanup​

Clean up associated resources:

  • Configuration Removal: Remove processing configurations
  • Resource Deallocation: Free up processing resources
  • Storage Cleanup: Clean up associated storage and metadata
  • Access Control: Remove access permissions and controls

Delete Nexset Endpoint​

To delete a specific Nexset:

DELETE /nexsets/{nexset_id}
Delete Nexset: Request
DELETE /nexsets/3001

Delete Response​

A successful deletion returns confirmation:

Delete Nexset: Response
{
  "status": "success",
  "message": "Nexset deleted successfully",
  "deleted_id": 3001,
  "deletion_info": {
    "deleted_at": "2023-01-16T21:00:00.000Z",
    "deleted_by": 42,
    "deletion_reason": "Workflow consolidation"
  },
  "cleanup_summary": {
    "configurations_removed": 1,
    "resources_freed": 4,
    "storage_cleaned": "2.5 GB",
    "dependencies_checked": true
  }
}

Bulk Delete Operations​

Remove multiple Nexsets simultaneously for efficient cleanup.

Bulk Delete Endpoint​

To delete multiple Nexsets:

DELETE /nexsets/bulk_delete
Bulk Delete: Request
DELETE /nexsets/bulk_delete

{
  "nexset_ids": [3001, 3002, 3003],
  "deletion_reason": "System consolidation",
  "force_delete": false
}

Bulk Delete Response​

Bulk deletion returns confirmation for all deleted Nexsets:

Bulk Delete: Response
{
  "status": "success",
  "message": "Bulk deletion completed successfully",
  "deleted_count": 3,
  "deletion_summary": {
    "successful_deletions": 3,
    "failed_deletions": 0,
    "total_resources_freed": 12,
    "total_storage_cleaned": "7.8 GB"
  },
  "results": [
    {
      "id": 3001,
      "status": "deleted",
      "result": "success"
    },
    {
      "id": 3002,
      "status": "deleted",
      "result": "success"
    },
    {
      "id": 3003,
      "status": "deleted",
      "result": "success"
    }
  ]
}

Conditional Deletion​

Delete Nexsets based on specific criteria and conditions.

Delete by Criteria​

Delete Nexsets matching specific criteria:

Delete by Criteria: Request
DELETE /nexsets/conditional_delete

{
  "criteria": {
    "status": "INACTIVE",
    "created_before": "2023-01-01T00:00:00.000Z",
    "owner_id": 42,
    "processing_mode": "batch"
  },
  "deletion_reason": "Cleanup of inactive batch Nexsets"
}

Conditional Delete Response​

Conditional deletion returns summary of deleted Nexsets:

Conditional Delete: Response
{
  "status": "success",
  "message": "Conditional deletion completed",
  "deleted_count": 8,
  "criteria_applied": {
    "status": "INACTIVE",
    "created_before": "2023-01-01T00:00:00.000Z",
    "owner_id": 42,
    "processing_mode": "batch"
  },
  "cleanup_summary": {
    "total_resources_freed": 24,
    "total_storage_cleaned": "15.2 GB",
    "dependencies_checked": true
  }
}

Deletion Considerations​

Understanding when and how to delete Nexsets helps you maintain an effective data processing infrastructure.

When to Delete Nexsets​

Appropriate scenarios for Nexset deletion:

  • Workflow Consolidation: Consolidate similar processing workflows
  • System Cleanup: Remove outdated or unused workflows
  • Resource Management: Free up resources for new workflows
  • Maintenance: Clean up during system maintenance
  • Decommissioning: Remove workflows during system decommissioning

Deletion Precautions​

Important considerations before deleting Nexsets:

  • Dependency Analysis: Ensure no systems depend on the Nexset
  • Data Backup: Backup important configurations and data
  • Impact Assessment: Assess impact on data processing pipelines
  • Team Coordination: Coordinate deletions across team members
  • Rollback Planning: Plan for potential rollback scenarios

Deletion Strategies​

Implement effective strategies for Nexset cleanup.

Gradual Cleanup​

Establish gradual cleanup procedures:

  • Inactive Nexsets: Remove Nexsets that have been inactive for extended periods
  • Unused Workflows: Remove workflows that are no longer referenced
  • Resource Optimization: Remove Nexsets to optimize resource utilization
  • Performance Improvement: Remove Nexsets that impact system performance

Selective Deletion​

Use selective deletion for targeted cleanup:

  • By Status: Remove Nexsets with specific operational status
  • By Age: Remove Nexsets older than specified time periods
  • By Owner: Remove Nexsets owned by specific users
  • By Type: Remove Nexsets of specific processing types

Deletion Workflows​

Implement structured workflows for safe Nexset deletion.

Individual Deletion Workflow​

Standard workflow for deleting individual Nexsets:

  1. Dependency Check: Verify no systems depend on the Nexset
  2. Impact Assessment: Assess impact on data processing pipelines
  3. Data Backup: Backup important configurations and data
  4. Deletion Execution: Execute deletion operation
  5. Cleanup Verification: Verify successful cleanup and resource release

Bulk Deletion Workflow​

Workflow for bulk Nexset cleanup:

  1. Criteria Definition: Define deletion criteria and conditions
  2. Impact Analysis: Analyze impact on data processing infrastructure
  3. Dependency Mapping: Map dependencies across all affected Nexsets
  4. Deletion Execution: Execute bulk deletion operation
  5. Cleanup Verification: Verify successful cleanup of all resources

Deletion Best Practices​

To effectively delete Nexsets in your Nexla platform:

  1. Assess Dependencies: Thoroughly assess dependencies before deletion
  2. Backup Important Data: Backup configurations and data that may be needed
  3. Plan Deletion Timing: Plan deletions during low-impact periods
  4. Monitor Impact: Monitor system impact during and after deletion
  5. Document Procedures: Maintain clear deletion procedures and responses

Deletion Impact​

Understanding the impact of Nexset deletion helps you make informed decisions.

Immediate Effects​

Immediate consequences of Nexset deletion:

  • Resource Release: Immediate release of processing resources
  • Configuration Removal: Removal of processing configurations
  • Access Control: Removal of access permissions and controls
  • Storage Cleanup: Cleanup of associated storage and metadata

Long-Term Effects​

Long-term implications of deletion:

  • Pipeline Impact: Potential impact on data processing pipelines
  • Resource Optimization: Improved resource utilization and performance
  • Maintenance Reduction: Reduced maintenance overhead and complexity
  • System Cleanliness: Improved system organization and clarity

Error Handling​

Common deletion issues and solutions:

  • Dependency Conflicts: Resolve dependencies before deletion
  • Permission Denied: Ensure you have appropriate deletion rights
  • Resource Locked: Check if Nexset is currently in use
  • Bulk Operation Failures: Verify deletion criteria and conditions

After deleting Nexsets, you may need to:

Verify Cleanup​

GET /nexsets
GET /resources/allocated

Monitor System Impact​

GET /system/performance
GET /system/resources

Restore if Needed​

# Note: Deleted Nexsets cannot be restored
# Consider archiving important configurations before deletion

Update Dependencies​

PUT /data_sources/{source_id}
PUT /data_sinks/{sink_id}