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 the upcoming v1.9, we should deprecate the old s3 connector. We can retain its code for backward compatibility in the short term, but renaming it to 's3_deprecate'. Additionally, we can remove its document to avoid misuse.
In the meanwhile, we should rename s3_v2 to s3, making it the default implementation.
The text was updated successfully, but these errors were encountered:
I agree with the purpose of deprecating legacy s3 connector but I don't think renaming it to an existing connector name is desirable. It may cause some trouble handing compatibility.
How about just refuse the requests for s3 connector and tell them use s3_v2 instead.
In the upcoming v1.9, we should deprecate the old
s3
connector. We can retain its code for backward compatibility in the short term, but renaming it to 's3_deprecate'. Additionally, we can remove its document to avoid misuse.In the meanwhile, we should rename
s3_v2
tos3
, making it the default implementation.The text was updated successfully, but these errors were encountered: