This topic compares the old and new versions of shipping to OSS and explains the upgrade process.
Version comparison
|
Item |
Old version |
New version |
|
Data shipping time range |
Ships data generated after the shipping job is created. |
|
|
Number of jobs |
You can create only one shipping job per Logstore. |
You can create multiple shipping jobs per Logstore. |
|
Time zone support for date-based directories |
Not supported |
Supported |
|
Compression type |
snappy |
snappy, gzip, and zstd |
|
File format |
JSON, CSV, and Parquet |
JSON, CSV, Parquet, and ORC |
|
Dashboard |
Not supported |
Supported |
|
Monitoring and alerting |
Not supported |
Supported |
|
Pause and resume jobs |
Not supported |
Supported |
|
Shipping latency |
Not supported |
Supported |
Migrate to the new version
The old and new versions of shipping to OSS run in parallel and share the same entry point. Follow these steps to migrate.
-
Stop the old shipping job.
-
Create a new shipping job.
For more information, see Create an OSS data shipping job (new version).
ImportantWhen configuring the Start At parameter for the new job, set the start time 5 to 15 minutes before you stop the old job. The exact offset depends on the old job's Shipping Interval. This method prevents data loss but may cause minor data duplication.
For example, if the old job's Shipping Interval is 300 seconds and you stop it at 12:00:00 on December 20, 2023, set Start At for the new job to 2023-12-20 11:55:00.