IoT File Service version 4.x – What’s New? - Developer Documentation
Skip to content

Version 4.x - What's New?

The IoT File Service empowers users with efficient file management capabilities tailored for assets. This service offers a user-friendly interface for data management, file searching, and downloading files associated with specific assets or agents. As the usage of the File Service grows over time, it's essential to address storage limitations to ensure optimal performance.

With the introduction of version 4.x, users gain access to the IoT File Service Bulk Delete API. This API allows users to systematically remove files from storage at regular intervals, aiding in the maintenance of service performance. To initiate bulk file deletion, users are required to create a Time To Live(TTL) rule. The TTL rule specifies the duration after which files are automatically deleted by the system. This rule operates on a daily basis, identifying and removing files that meet the criteria outlined in the rule

The V4.x API is designed with a primary focus on delivering intelligent and enhanced performance compared to the current Bulk Delete APIs.

Key features include: - The V4.x API streamlines the process of cleaning up file storage at regular intervals - Users benefit from an automated provision to delete files from the storage, simplifying the maintenance process, free up space and ensure that you have enough room for new files. - Users can easily configure criteria for file deletion, specifying the number of days as the chosen parameter - The API allows users to set up rules specifically for selected assets, providing a more tailored approach to file management - Users enjoy the flexibility of deleting files without any imposed restrictions on the number or size of files, offering a seamless and unrestricted experience - By regularly deleting files, you can improve the speed and performance of your device.

Concurrently, given that this involves the deletion of files from storage, it is crucial to take certain considerations into account to prevent any unforeseen behavior.

- Deletion operations are executed based on the last updated date of files in storage. Performing operations on older files that meet the deletion criteria may result in unpredictable outcomes, as the last updated date of the file would be altered
- The file storage system operates on an eventual consistency model. Although there may be temporary inconsistencies, both files and metadata will eventually attain a consistent state
- Any modifications made to the Time To Live (TTL) rule will only take effect during the subsequent rule execution cycle. Users should be aware that changes to the rule may not be immediately reflected

We recommend users to make use of File Service Bulk Delete APIs to delete the files from the storage for improved performance. For information on how to use the 4.x API, refer to Bulk Delete Operation

Bulk Delete Operation

Process flow

Create TTL Rule

User to create TTL rule by providing

- Specific path(asset)
- Number of days after which data should be deleted

Last update: December 8, 2023

Except where otherwise noted, content on this site is licensed under the Development License Agreement.