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 Apache Flink we are using PrestoS3FileSystem. We recently updated from presto-hive 0.187 to 0.257. This brought in a change of behavior in case credentials were missing. In our testcase, we intentionally provide no credentials and then check that #exists() on a path fails. We specifically asserted on an IOException here.
Somewhere between 0.187 and 0.257, PrestoS3FileSystem#initialize was changed to call createAwsCredentialsProvider. Now if credentials are missing, this already fails and throws an SdkClientException instead.
I'm not sure whether you consider this correct or not, but since presto uses IOException in many places and this has now changed I wanted to report it in case you consider this an unintended change in behavior.
Sorry for the noise. My description above is incorrect, and should've read
Somewhere between 0.187 and 0.257, PrestoS3FileSystem was changed to use DefaultAWSCredentialsProviderChain in #createAwsCredentialsProvider rather than throwing an exception in what was then called getAwsCredentialsProvider.
However, even then it was a RuntimeException, not an IOException, so the point is moot for presto.
In Apache Flink we are using PrestoS3FileSystem. We recently updated from presto-hive 0.187 to 0.257. This brought in a change of behavior in case credentials were missing. In our testcase, we intentionally provide no credentials and then check that
#exists()
on a path fails. We specifically asserted on anIOException
here.Somewhere between 0.187 and 0.257,
PrestoS3FileSystem#initialize
was changed to callcreateAwsCredentialsProvider
. Now if credentials are missing, this already fails and throws anSdkClientException
instead.I'm not sure whether you consider this correct or not, but since presto uses
IOException
in many places and this has now changed I wanted to report it in case you consider this an unintended change in behavior.References:
The text was updated successfully, but these errors were encountered: