You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some S3-compatible object storage systems the concept of a region as in S3 does not exist. One such example is MinIO. Currently users are forced to provide a fake value for region with these systems.
The desire is to make the region parameter optional. This could be done on the generic S3 level or potentially looking at creating separate levels for each "s3-compatible" system.
The text was updated successfully, but these errors were encountered:
But even if the SDK requires it .. we could shadow this in Trino and fill it in with some random value if minio is used, right?
Or we could just have a random and invalid default value. Then its essentially optional.. problem of course is that it is then quietly invalid for s3 users unless they fill it to correct the default.
In some S3-compatible object storage systems the concept of a region as in S3 does not exist. One such example is MinIO. Currently users are forced to provide a fake value for region with these systems.
The desire is to make the region parameter optional. This could be done on the generic S3 level or potentially looking at creating separate levels for each "s3-compatible" system.
The text was updated successfully, but these errors were encountered: