Remove legacy file system support #24878
Description
Part of the introduction of the new file system support lead by @electrum was always to get rid of the legacy systems that support S3 and others via the legacy Hive/HDFS libraries in 2025. The following file systems will remain after the removal
- New S3 file system support - https://trino.io/docs/current/object-storage/file-system-s3.html
- New Azure file system support - https://trino.io/docs/current/object-storage/file-system-azure.html
- New Google file system support - https://trino.io/docs/current/object-storage/file-system-gcs.html
- Hive/HDFS file system support for HDFS usage only - https://trino.io/docs/current/object-storage/file-system-hdfs.html
After discussion in Slack and in person we now have the following plan.
Early in 2025:
- Deprecate IBM COS support - Deprecate support for IBM COS via Hive #24870 -- part of Trino 470
- Deprecate legacy Azure storage support - Deprecate legacy Azure storage support #24871 -- part of Trino 470
- Deprecate legacy GCS storage support - Deprecate legacy GCS support via Hive #24879 -- part of Trino 470
- Deprecate legacy S3 storage support - Deprecate the legacy S3 storage support #24880 -- part of Trino 470
- Write a blog post about the removal once all four are available in releases - available at https://trino.io/blog/2025/02/10/old-file-system
These deprecations are doing the following:
- Deprecate all properties
- Remove documentation
- Update or remove tests as needed
- Question for @electrum - should the migration guides be moved to the docs for the new file system so we dont loose them (might be a pain to maintain and decide when to remove later) or should users just read that in the old docs (harder to find for users but we could hardcode a link to a specific older version if we want) - we decided to move that, that is also part of 470
As a result users will see warnings about using any of the deprecated properties in their Trino startup. We will review any user feedback for missing features in the new file system support, but we will NOT reactivate these systems. They will be removed. If there are missing features that need to be added we will work with the community to ideally add them before removing the legacy system, however we will not add any feature.
Later in 2025, potentially as early as March with the upgrade to Java 24, we will proceed with the following steps:
- Remove all the deprecated file systems from the codebase completely.
- Write another blog post (or update the prior one with a note).