Document trailing slash change due to native S3 file system

[jonashartwig]

Hi,

We just updated from Trino 433 to 466. In doing so we switched over from legacy S3 implementation to the new native one (using it through the Hive connector). We use the security mapping document to map buckets and groups to access keys. In the new file system the prefix parsing works differently.

One mapping item from version 433 looks like this and is verified to work:

{
    "group": "G",
    "accessKey": "AK",
    "secretKey": "????",
    "prefix": "s3://data-bucket-think"
}

However in the new implementation it is now required to have a path in the prefix like this (note the trailing /):

{
    "group": "G",
    "accessKey": "AK",
    "secretKey": "????",
    "prefix": "s3://data-bucket-think/"
}

Using a path (e.g. trailing /) also works in the legacy file system, however it worked without and is now required.

I think I read the release log quite thoroughly (especially in regards to breaking changes) and this behavioral change was missed.

Should this be added as a note somewhere?

regards