Skip to main content

Update Nexset

Updating Nexsets in Nexla allows you to modify configuration settings, processing logic, and operational parameters to adapt your data processing workflows to changing requirements and optimize performance.

Nexset Update Overview​

Nexset updates enable you to evolve your data processing workflows over time, implementing new business logic, optimizing performance, and adapting to changing data structures and requirements.

Update Nexset Endpoint​

To update an existing Nexset:

PUT /nexsets/{nexset_id}
Update Nexset: Request
PUT /nexsets/3001

{
  "name": "Enhanced Customer Data Enrichment",
  "description": "Enhanced customer data enrichment with additional behavioral analytics",
  "transforms": [3001, 3002, 3005],
  "config": {
    "processing_mode": "streaming",
    "batch_size": 2000,
    "error_handling": "continue_on_error",
    "parallelism": 4
  }
}

Update Response​

A successful update returns the updated Nexset configuration:

Update Nexset: Response
{
  "id": 3001,
  "name": "Enhanced Customer Data Enrichment",
  "description": "Enhanced customer data enrichment with additional behavioral analytics",
  "input_schema_id": 2001,
  "output_schema_id": 2002,
  "transforms": [3001, 3002, 3005],
  "config": {
    "processing_mode": "streaming",
    "batch_size": 2000,
    "error_handling": "continue_on_error",
    "parallelism": 4
  },
  "status": "ACTIVE",
  "created_at": "2023-01-15T10:00:00.000Z",
  "updated_at": "2023-01-16T15:30:00.000Z",
  "owner": {
    "id": 42,
    "full_name": "John Smith"
  }
}

Updateable Fields​

Fields that can be modified during Nexset updates:

  • name: Nexset name and identifier
  • description: Detailed description of the Nexset
  • transforms: Array of transform IDs to apply
  • config: Processing configuration and parameters
  • tags: Metadata tags for organization
  • metadata: Additional custom metadata

Configuration Updates​

Modify processing configuration to optimize performance and behavior.

Processing Mode Updates​

Change how the Nexset processes data:

  • Streaming Mode: Real-time data processing
  • Batch Mode: Batch data processing
  • Hybrid Mode: Combination of streaming and batch

Performance Optimization​

Optimize processing performance:

  • Batch Size: Adjust number of records per batch
  • Parallelism: Configure parallel processing threads
  • Memory Limits: Set memory allocation limits
  • Caching: Configure data caching strategies

Error Handling Updates​

Modify error handling behavior:

  • Continue on Error: Continue processing despite errors
  • Stop on Error: Stop processing when errors occur
  • Retry Logic: Implement retry mechanisms
  • Error Logging: Configure error logging and reporting

Transform Updates​

Modify the transformation logic applied to your data.

Transform Addition​

Add new transforms to the processing pipeline:

Add Transform: Request
PUT /nexsets/3001

{
  "transforms": [3001, 3002, 3005, 3006]
}

Transform Removal​

Remove transforms from the processing pipeline:

Remove Transform: Request
PUT /nexsets/3001

{
  "transforms": [3001, 3002]
}

Transform Reordering​

Change the order of transform application:

Reorder Transforms: Request
PUT /nexsets/3001

{
  "transforms": [3002, 3001, 3005]
}

Schema Updates​

Modify input and output schemas for your Nexset.

Input Schema Updates​

Update the input data structure:

Update Input Schema: Request
PUT /nexsets/3001

{
  "input_schema_id": 2003
}

Output Schema Updates​

Update the output data structure:

Update Output Schema: Request
PUT /nexsets/3001

{
  "output_schema_id": 2004
}

Partial Updates​

Update specific fields without affecting others.

Name and Description Updates​

Update basic identification information:

Update Name and Description: Request
PUT /nexsets/3001

{
  "name": "Updated Customer Enrichment",
  "description": "Updated description with new features"
}

Configuration Updates​

Update specific configuration parameters:

Update Configuration: Request
PUT /nexsets/3001

{
  "config": {
    "batch_size": 3000,
    "parallelism": 6
  }
}

Update Considerations​

Important considerations when updating Nexsets.

Impact Assessment​

Assess the impact of updates:

  • Data Flow Impact: Understand how changes affect data processing
  • Performance Impact: Assess performance implications of changes
  • Downstream Impact: Consider effects on dependent systems
  • Rollback Planning: Plan for potential rollback scenarios

Validation Requirements​

Validate updates before deployment:

  • Schema Compatibility: Ensure schema changes are compatible
  • Transform Validation: Verify transform functionality
  • Configuration Validation: Validate configuration parameters
  • Integration Testing: Test end-to-end functionality

Update Workflows​

Implement structured workflows for effective Nexset updates.

Planning Phase​

Plan your Nexset updates:

  1. Requirement Analysis: Define update requirements and objectives
  2. Impact Assessment: Assess impact on data processing and downstream systems
  3. Testing Planning: Plan comprehensive testing of updates
  4. Rollback Planning: Plan rollback procedures if needed

Implementation Phase​

Implement your Nexset updates:

  1. Configuration Updates: Update Nexset configuration parameters
  2. Transform Updates: Modify transformation logic and pipeline
  3. Schema Updates: Update input and output schemas
  4. Validation Testing: Test update functionality and performance

Deployment Phase​

Deploy your Nexset updates:

  1. Staging Deployment: Deploy updates to staging environment
  2. Production Deployment: Deploy updates to production environment
  3. Monitoring: Monitor performance and functionality after deployment
  4. Verification: Verify that updates meet requirements and objectives

Update Best Practices​

To effectively update Nexsets in your Nexla platform:

  1. Plan Thoroughly: Carefully plan updates and assess impact
  2. Test Comprehensively: Test updates in development and staging environments
  3. Monitor Performance: Monitor performance after updates
  4. Document Changes: Maintain clear documentation of all updates
  5. Plan Rollbacks: Have rollback procedures ready if needed

Error Handling​

Common Nexset update issues and solutions:

  • Schema Mismatch: Ensure schema updates are compatible with existing data
  • Transform Errors: Verify transform configuration and functionality
  • Configuration Issues: Check configuration parameter values and formats
  • Permission Denied: Ensure you have appropriate update rights

After updating a Nexset, you may need to:

Validate Updates​

POST /nexsets/{nexset_id}/validate
GET /nexsets/{nexset_id}/samples

Test Processing​

POST /nexsets/{nexset_id}/test
GET /nexsets/{nexset_id}/metrics

Monitor Performance​

GET /nexsets/{nexset_id}/status
GET /nexsets/{nexset_id}/performance

Rollback if Needed​

PUT /nexsets/{nexset_id}
# Restore previous configuration