Skip to content

GH-32123: [R] Expose azure blob filesystem#49553

Open
marberts wants to merge 85 commits into
apache:mainfrom
marberts:32123-expose-azure-blob-filesystem
Open

GH-32123: [R] Expose azure blob filesystem#49553
marberts wants to merge 85 commits into
apache:mainfrom
marberts:32123-expose-azure-blob-filesystem

Conversation

@marberts

@marberts marberts commented Mar 19, 2026

Copy link
Copy Markdown
Contributor

Rationale for this change

This PR adds support for Azure. The Arrow R package already has support for AWS and GCS, and the Arrow C++ library has had support for Azure for a couple years now. Support for Azure is already available in pyarrow.

This would close #32123.

What changes are included in this PR?

  • A new class AzureFileSystem that's analogous to S3FileSystem/GcsFileSystem, along with a helper function az_container() that's analogous to s3_bucket()/gcs_bucket().

  • Updates to src/filesystem.cpp to interact with the machinery in arrow/filesystem/azurefs.h.

  • Updates to the configuration and build scripts to support building with support for Azure.

  • Updates to the vignettes on cloud storage, installation, and developer setup.

Are these changes tested?

Yes. See tests/testthat/test-azure.R.

Are there any user-facing changes?

Yes. There is a new function az_container(), serving the analogous role to s3_bucket()/gcs_bucket(), along with an R6 class AzureFileSystem, again serving the same role as S3FileSystem and GcsFileSystem. There is also a function arrow_with_azure() to indicate if Arrow was built with support for Azure.

@github-actions

Copy link
Copy Markdown

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:

@marberts marberts changed the title 32123 expose azure blob filesystem GH-32123 [R]: Expose azure blob filesystem Mar 19, 2026
@marberts marberts changed the title GH-32123 [R]: Expose azure blob filesystem GH-32123: [R] Expose azure blob filesystem Mar 19, 2026
@github-actions

Copy link
Copy Markdown

⚠️ GitHub issue #32123 has been automatically assigned in GitHub to PR creator.

@marberts

marberts commented Mar 20, 2026

Copy link
Copy Markdown
Contributor Author

The CI is failing because the Azure C++ SDK depends on libxml2.

  • Update tools/nixlibs.R to check for libxml2 in with_cloud_support(), turning off the Azure feature flag if libxml2 isn't found.
    • What about configure and configure.win?
    • Is with_cloud_support() the only function that needs changing in tools/nixlibs.R?
  • Update the install.Rmd and developers/setup.Rmd vignettes to note that libxml2 is a dependency of Azure (same as with curl and openssl).
  • Update DESCRIPTION to include libxml2 in SystemRequirements.

@marberts

Copy link
Copy Markdown
Contributor Author

It looks like the failing CI job is from a warning in R CMD check about a non-API call to a C function, due to all the changes in R-devel. I don't think this is due to our PR.

At this point, I'm fairly confident that we've implemented the Azure features correctly. The only thing I'm not sure about is the setup in configure, configure.win, and tools/nixlibs.R. The Azure C++ SDK used by Arrow requires libxml2, which is a new system dependency for this package. I don't fully understand how these configuration scripts work, so I wouldn't be surprised if they're not updated correctly to reflect the new system dependency.

@jonkeane, @thisisnic, @assignUser Please let me or @Collinbrown95 know if there are any changes needed to this PR.

@thisisnic

Copy link
Copy Markdown
Member

Thanks for the PR @marberts - if you rebase from the main branch now, the non-API call stuff should be resolved.

Your best bet for the configure etc stuff is looking at the history of that file or older PRs to see how this kind of thing was handled there.

This PR where the GCS bindings were added might help: #13404, but let us know if you have any questions!

@thisisnic

Copy link
Copy Markdown
Member

We'll also need additional CI jobs to test this - the PR I linked to above contains examples of what we added there.

@marberts

Copy link
Copy Markdown
Contributor Author

Great, thanks @thisisnic!

@marberts

marberts commented Mar 24, 2026

Copy link
Copy Markdown
Contributor Author

To do list.

@marberts marberts marked this pull request as draft March 25, 2026 23:32
@Collinbrown95

Copy link
Copy Markdown

@github-actions crossbow submit -g r

@github-actions

Copy link
Copy Markdown
Only contributors can submit requests to this bot. Please ask someone from the community for help with getting the first commit in.
The Archery job run can be found at: https://github.com/apache/arrow/actions/runs/23576717645

@thisisnic

Copy link
Copy Markdown
Member

@github-actions crossbow submit -g r

@github-actions

Copy link
Copy Markdown

Revision: 4da7280

Submitted crossbow builds: ursacomputing/crossbow @ actions-92325d6543

Task Status
r-binary-packages GitHub Actions
r-recheck-most GitHub Actions
test-r-alpine-linux-cran GitHub Actions
test-r-arrow-backwards-compatibility GitHub Actions
test-r-depsource-system GitHub Actions
test-r-dev-duckdb GitHub Actions
test-r-devdocs GitHub Actions
test-r-extra-packages GitHub Actions
test-r-fedora-clang GitHub Actions
test-r-gcc-11 GitHub Actions
test-r-gcc-12 GitHub Actions
test-r-install-local GitHub Actions
test-r-install-local-minsizerel GitHub Actions
test-r-linux-as-cran GitHub Actions
test-r-linux-rchk GitHub Actions
test-r-linux-sanitizers GitHub Actions
test-r-linux-valgrind GitHub Actions
test-r-m1-san GitHub Actions
test-r-macos-as-cran GitHub Actions
test-r-offline-maximal GitHub Actions
test-r-ubuntu-22.04 GitHub Actions
test-r-versions GitHub Actions

@marberts

Copy link
Copy Markdown
Contributor Author

@github-actions crossbow submit -g r

@github-actions

Copy link
Copy Markdown
Only contributors can submit requests to this bot. Please ask someone from the community for help with getting the first commit in.
The Archery job run can be found at: https://github.com/apache/arrow/actions/runs/23698292050

@thisisnic

Copy link
Copy Markdown
Member

Some of those CI failures are from things which have been fixed on main - you'll need to rebase your branch.

Collinbrown95 and others added 27 commits June 26, 2026 21:42
Note: I think what's happening is that the build of Arrow I install doesn't have the ARROW_AZURE flag enabled. When I "force" the environment variable I get an error like "fs___AzureFileSystem__Make not found".
Note: this was causing a seg fault when anything that inherits from FileSystem ries to access the base_path property. Uncommenting the return line and rebuilding the R package resolved this issue.
At this point, I was able to call write_feather(example_data, fs$path("test/test.feather")) successfully against Azurite.

Committing progress before I make any further changes.
Switch over  to locally hosted azurite instead of local docker container azurite.
The hypothesis is that the errors in the build logs are caused by incompatibilities between WIL (Windows Implementation Library) and MinGW GCC, so install them directly instead of trying to build from source.
@marberts marberts force-pushed the 32123-expose-azure-blob-filesystem branch from 46a4770 to c728602 Compare June 27, 2026 02:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[R] Expose Azure Blob Storage filesystem

5 participants