FlowX.AI v5.3.0 is an incremental update from v5.2.0 with one breaking change related to FlowX Engine configuration structure.
What’s changing
FlowX.AI v5.3.0 introduces a breaking change to the FlowX Engine partitioning and archiving configuration structure. Thescheduler.dataPartitioning section has been removed, and archiving settings have been reorganized under partitioning.archiving.
Who is affected
Migration process
1
Review configuration changes
Understand the new configuration structure and identify which settings need to be updated in your deployment
2
Update configuration files
Update your FlowX Engine configuration files (YAML or environment variables) following the migration steps
3
Deploy and verify
Deploy the updated configuration and verify that partitioning and archiving continue to work correctly
Key changes summary
Configuration structure
What’s removed:scheduler.dataPartitioningsection withenabledandcronExpressionsettings
partitioning.archivingsubsection containing all archiving-related settings
retention-intervalsmoved frompartitioningtopartitioning.archivingdetached-partition-compressionmoved topartitioning.archivingmoved-data-batch-sizemoved topartitioning.archivingcronExpressionmoved fromscheduler.dataPartitioningtopartitioning.archiving
Environment variables
5 environment variables have been renamed to reflect the new structure:| Old Variable | New Variable |
|---|---|
SCHEDULER_DATAPARTITIONING_ENABLED | FLOWX_DATA_PARTITIONING_ARCHIVING_ENABLED |
SCHEDULER_DATAPARTITIONING_CRONEXPRESSION | FLOWX_DATA_PARTITIONING_ARCHIVING_CRONEXPRESSION |
FLOWX_DATA_PARTITIONING_RETENTION_INTERVALS | FLOWX_DATA_PARTITIONING_ARCHIVING_RETENTIONINTERVALS |
FLOWX_DATA_PARTITIONING_DETACHED_PARTITION_COMPRESSION | FLOWX_DATA_PARTITIONING_ARCHIVING_DETACHED_PARTITION_COMPRESSION |
FLOWX_DATA_PARTITIONING_MOVED_DATA_BATCH_SIZE | FLOWX_DATA_PARTITIONING_ARCHIVING_MOVED_DATA_BATCH_SIZE |
Backward compatibility
Rollback support
If you need to rollback from v5.3.0 to v5.2.x:- Revert your configuration files to the previous structure
- Restore environment variables to their previous names
- Downgrade the FlowX Engine container/pod to the previous version
Database schema changes are forward-compatible. Ensure you have database backups before any upgrade.
This is a configuration-only change. No code changes, data migration, or schema updates are required.
Next steps
Additional resources
Partitioning & Archiving Setup
Complete guide to FlowX Engine partitioning and archiving
Deployment Guidelines v5.3.0
Component versions and deployment instructions
Release Notes v5.3.0
Full release notes for v5.3.0
Support
For technical support, deployment assistance, or migration questions, contact your FlowX.AI support representative.

