Skip to main content
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. The scheduler.dataPartitioning section has been removed, and archiving settings have been reorganized under partitioning.archiving.

Who is affected

This breaking change only affects deployments that have:
  • Enabled data partitioning in FlowX Engine (FLOWX_DATA_PARTITIONING_ENABLED=true)
  • Configured archiving settings (SCHEDULER_DATAPARTITIONING_ENABLED=true)
If you have not enabled these features, you should still update your configuration files for future compatibility, but there is no immediate operational impact.

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.dataPartitioning section with enabled and cronExpression settings
What’s added:
  • partitioning.archiving subsection containing all archiving-related settings
What’s moved:
  • retention-intervals moved from partitioning to partitioning.archiving
  • detached-partition-compression moved to partitioning.archiving
  • moved-data-batch-size moved to partitioning.archiving
  • cronExpression moved from scheduler.dataPartitioning to partitioning.archiving

Environment variables

5 environment variables have been renamed to reflect the new structure:
Old VariableNew Variable
SCHEDULER_DATAPARTITIONING_ENABLEDFLOWX_DATA_PARTITIONING_ARCHIVING_ENABLED
SCHEDULER_DATAPARTITIONING_CRONEXPRESSIONFLOWX_DATA_PARTITIONING_ARCHIVING_CRONEXPRESSION
FLOWX_DATA_PARTITIONING_RETENTION_INTERVALSFLOWX_DATA_PARTITIONING_ARCHIVING_RETENTIONINTERVALS
FLOWX_DATA_PARTITIONING_DETACHED_PARTITION_COMPRESSIONFLOWX_DATA_PARTITIONING_ARCHIVING_DETACHED_PARTITION_COMPRESSION
FLOWX_DATA_PARTITIONING_MOVED_DATA_BATCH_SIZEFLOWX_DATA_PARTITIONING_ARCHIVING_MOVED_DATA_BATCH_SIZE

Backward compatibility

No backward compatibility: The old configuration structure is not supported in v5.3.0 and causes FlowX Engine startup errors.You must update your configuration before or immediately after upgrading to v5.3.0.

Rollback support

If you need to rollback from v5.3.0 to v5.2.x:
  1. Revert your configuration files to the previous structure
  2. Restore environment variables to their previous names
  3. 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

Support

For technical support, deployment assistance, or migration questions, contact your FlowX.AI support representative.