| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Thanks for opening a pull request! If this is not a minor PR. Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose Opening GitHub issues ahead of time contributes to the Openness of the Apache Arrow project. Then could you also rename the pull request title in the following format? GH-${GITHUB_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}
or MINOR: [${COMPONENT}] ${SUMMARY}
See also: |
Sorry, something went wrong.
|
⚠️ GitHub issue #42173 has been automatically assigned in GitHub to PR creator. |
Sorry, something went wrong.
|
⚠️ GitHub issue #42173 has been automatically assigned in GitHub to PR creator. |
Sorry, something went wrong.
|
Hi, @jonkeane @thisisnic thanks for any comment || review |
Sorry, something went wrong.
|
⚠️ GitHub issue #42173 has been automatically assigned in GitHub to PR creator. |
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks for making this PR @simonelbaz! I've given it a look over, and it looks like there's an existing option for this scenario that might be a better solution, though I haven't tried it out myself - let me know what you think.
Sorry, something went wrong.
|
⚠️ GitHub issue #42173 has been automatically assigned in GitHub to PR creator. |
Sorry, something went wrong.
…d if ListBucket is not allowed for the user
…3 failed if ListBucket is not allowed for the user
…3 failed if ListBucket is not allowed for the user
Co-authored-by: Antoine Pitrou <pitrou@free.fr>
There was a problem hiding this comment.
+1 from me. @thisisnic Are you ok with the new argument name and docstring?
Sorry, something went wrong.
|
Hi @thisisnic, thanks for any feedback or comment on the PR. |
Sorry, something went wrong.
There was a problem hiding this comment.
Great, thanks!
Sorry, something went wrong.
|
⚠️ GitHub issue #42173 has been automatically assigned in GitHub to PR creator. |
Sorry, something went wrong.
|
After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit b808fbb. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 8 possible false positives for unstable benchmarks that are known to sometimes produce them. |
Sorry, something went wrong.
…istBucket is not allowed for the user (apache#47599) ### Rationale for this change This PR gives the user to choose not to create directory in the bucket before writing dataset. In case the `create_directory` option is set to FALSE, no verification will be made by R arrow. The S3 storage will itself verify if the directory exists and if the users has the rigth to modify it. This way no `ListBucket` or ` HeadBucket` are necessary to achieve the write operation. ``` df |> arrow::write_dataset( minio$path(paste0("smartsla-bucket/rarrow/")), partitioning = "qualitative", create_directory = FALSE, format = "parquet" ) ``` ### What changes are included in this PR? `create_directory` is now available to the user in the `write_dataset` function. Before this PR, this option was automatically set to TRUE (by default). ### Are these changes tested? Yes ### Are there any user-facing changes? No, the default value for `create_directory` is still TRUE. * GitHub Issue: apache#42173 Lead-authored-by: Simon ELBAZ <elbazsimon9@gmail.com> Co-authored-by: Simon Elbaz <elbazsimon9@gmail.com> Co-authored-by: Antoine Pitrou <pitrou@free.fr> Signed-off-by: Antoine Pitrou <antoine@python.org>
…istBucket is not allowed for the user (apache#47599) ### Rationale for this change This PR gives the user to choose not to create directory in the bucket before writing dataset. In case the `create_directory` option is set to FALSE, no verification will be made by R arrow. The S3 storage will itself verify if the directory exists and if the users has the rigth to modify it. This way no `ListBucket` or ` HeadBucket` are necessary to achieve the write operation. ``` df |> arrow::write_dataset( minio$path(paste0("smartsla-bucket/rarrow/")), partitioning = "qualitative", create_directory = FALSE, format = "parquet" ) ``` ### What changes are included in this PR? `create_directory` is now available to the user in the `write_dataset` function. Before this PR, this option was automatically set to TRUE (by default). ### Are these changes tested? Yes ### Are there any user-facing changes? No, the default value for `create_directory` is still TRUE. * GitHub Issue: apache#42173 Lead-authored-by: Simon ELBAZ <elbazsimon9@gmail.com> Co-authored-by: Simon Elbaz <elbazsimon9@gmail.com> Co-authored-by: Antoine Pitrou <pitrou@free.fr> Signed-off-by: Antoine Pitrou <antoine@python.org>
| Back | FazBrowse Home | New Git URL |
Rationale for this change
This PR gives the user to choose not to create directory in the bucket before writing dataset.
In case the create_directory option is set to FALSE, no verification will be made by R arrow.
The S3 storage will itself verify if the directory exists and if the users has the rigth to modify it.
This way no ListBucket or HeadBucket are necessary to achieve the write operation.
df |> arrow::write_dataset( minio$path(paste0("smartsla-bucket/rarrow/")), partitioning = "qualitative", create_directory = FALSE, format = "parquet" )What changes are included in this PR?
create_directory is now available to the user in the write_dataset function.
Before this PR, this option was automatically set to TRUE (by default).
Are these changes tested?
Yes
Are there any user-facing changes?
No, the default value for create_directory is still TRUE.