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
<!--
Thanks for opening a pull request!
-->
<!-- In the case this PR will resolve an issue, please replace
${GITHUB_ISSUE_ID} below with the actual Github issue id. -->
<!-- Closes #${GITHUB_ISSUE_ID} -->
# Rationale for this change
This fix addressed issue #1922 and changed the behavior for both
`_oss_fs` and `_s3_fs` to be able to parse `s3.force-virtual-addressing`
correctly.
# Are these changes tested?
No unit tests are given to this change yet
# Are there any user-facing changes?
No
<!-- In the case of user-facing changes, please add the changelog label.
-->
| s3.access-key-id | admin | Configure the static access key id used to access the FileIO. |
190
190
| s3.secret-access-key | password | Configure the static secret access key used to access the FileIO. |
191
191
| s3.session-token | AQoDYXdzEJr... | Configure the static session token used to access the FileIO. |
192
-
| s3.force-virtual-addressing | True | Whether to use virtual addressing of buckets. This must be set to True as OSS can only be accessed with virtual hosted style address. |
192
+
| s3.force-virtual-addressing | True | Whether to use virtual addressing of buckets. This is set to `True` by default as OSS can only be accessed with virtual hosted style address. |
0 commit comments