GH-36886: [C++] Configure azurite in preparation for testing Azure C++ filesystem

[Tom-Newton]

Rationale for this change

We need to write tests for #18014. azurite is like a fake Azure blob storage so it can be used to write integration tests

What changes are included in this PR?

Extract the azurite related changes from #12914 to create a smaller PR that's easier to review. I have made very minimal changes compared to that PR.

Currently azurite is configured for all the environments where ARROW_AZURE was enabled by #35701. I assume its deliberate that its not enabled yet for windows, alpine, conda, debian or fedora builds.

Are these changes tested?

Its tested by there aren't really any good tests in this PR. I used this azurite config in #36835 to make an integration test that uses the Azure C++ SDK. On its own we can't really write tests for this azurite setup PR.

Are there any user-facing changes?

No

• Closes: [C++] Configure azurite in preparation for testing Azure C++ filesystem #36886

[github-actions]

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}

In the case of PARQUET issues on JIRA the title also supports:

PARQUET-${JIRA_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}

See also:

• Other pull requests
• Contribution Guidelines - How to contribute patches

[github-actions]

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

[kou]

Could you use

arrow/cpp/src/arrow/filesystem/gcsfs_test.cc

Lines 18 to 35 in 7cbbd3e

	#include <algorithm> // Missing include in boost/process
	#define BOOST_NO_CXX98_FUNCTION_BASE // ARROW-17805
	// This boost/asio/io_context.hpp include is needless for no MinGW
	// build.
	//
	// This is for including boost/asio/detail/socket_types.hpp before any
	// "#include <windows.h>". boost/asio/detail/socket_types.hpp doesn't
	// work if windows.h is already included. boost/process.h ->
	// boost/process/args.hpp -> boost/process/detail/basic_cmd.hpp
	// includes windows.h. boost/process/args.hpp is included before
	// boost/process/async.h that includes
	// boost/asio/detail/socket_types.hpp implicitly is included.
	#include <boost/asio/io_context.hpp>
	// We need BOOST_USE_WINDOWS_H definition with MinGW when we use
	// boost/process.hpp. See BOOST_USE_WINDOWS_H=1 in
	// cpp/cmake_modules/ThirdpartyToolchain.cmake for details.
	#include <boost/process.hpp>

?

[Tom-Newton]

I don't see a reason not to

[kou]

+1

[conbench-apache-arrow]

After merging your PR, Conbench analyzed the 6 benchmarking runs that have been run so far on merge-commit f055f5e.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about possible false positives for unstable benchmarks that are known to sometimes produce them.