Update trino config options to switch from deprecated hive settings
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	Dwisehaupt
	Sep 17 2025, 5:34 PM

Description

Seeing this in the logs after a trino restart:

Configuration should be updated:

1) Configuration property 'hive.s3.aws-access-key' is deprecated since 470 and will be removed in the future
2) Configuration property 'hive.s3.aws-secret-key' is deprecated since 470 and will be removed in the future
3) Configuration property 'hive.s3.endpoint' is deprecated since 470 and will be removed in the future
4) Configuration property 'hive.s3.path-style-access' is deprecated since 470 and will be removed in the future
5) Configuration property 'hive.s3.ssl.enabled' is deprecated since 470 and will be removed in the future

We should find out what the new config properties are and update them in our config before they are removed.

More info:

What's being deprecated is legacy S3 filesystem support by using libraries from hive/hadoop, see:

https://trino.io/blog/2025/02/10/old-file-system.html
https://github.com/trinodb/trino/issues/24878

The native filesystem support is supposed to work with hive/iceberg and should improve performance. At the bottom of this page, there's a migration guide for S3:

https://trino.io/docs/current/object-storage/file-system-s3.html

Event Timeline

Dwisehaupt created this task.Sep 17 2025, 5:34 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptSep 17 2025, 5:34 PM

https://trino.io/docs/current/object-storage/file-system-s3.html makes it seem straightforward, I think we would enable s.native-s3.enabled=true and remove the "hive." prefix from the deprecated s3 settings. Except the setting "hive.s3.ssl.enabled" is listed as one to remove, with no mention of what replaces it.

"hive.s3.ssl.enabled" isn't the issue, I think it's deprecated in favor of using the scheme from s3.endpoint

Here's the trino-cli error:

Error starting query at https://fransc2001.frack.codfw.wmnet:8443/v1/statement returned an invalid response: JsonResponse{statusCode=500, headers={content-length=[3641], content-type=[text/plain], date=[Wed, 17 Sep 2025 20:07:32 GMT], vary=[Accept-Encoding]}, hasValue=false} [Error: java.lang.IllegalStateException: authenticators were not loaded

So just swapping in new settings per "Migration from legacy S3 file system" isn't enough.

Jgreen updated the task description. (Show Details)Sep 17 2025, 8:29 PM

bug report submitted: https://github.com/trinodb/trino/issues/26664

The issue was caused by a missing s3.region setting.

Update trino config options to switch from deprecated hive settingsClosed, ResolvedPublicActions

Description

Event Timeline

Update trino config options to switch from deprecated hive settings
Closed, ResolvedPublic
Actions