Google Git
Sign in
apache / arrow / b235f83ed10bcad174b267113479a24ca045def5
commitb235f83ed10bcad174b267113479a24ca045def5[log] [tgz]
authorBenjamin Kietzman <bengilgit@gmail.com>Thu Mar 14 14:18:30 2024 -0400
committerGitHub <noreply@github.com>Thu Mar 14 14:18:30 2024 -0400
treee94d7856956e69dd0e9782307a6ef1ad2f9c222e
parent9035c4e0efaf07e5314ecef9c1a91e8291534c3b [diff]
GH-38309: [C++] build filesystems as separate modules (#39067)



### Rationale for this change

Each filesystem implementation carries unique and potentially heavy dependencies, so it'd be useful to build them separately. Furthermore, one typically doesn't need all of them at the same time and building separate modules would allow them to be dynamically loaded as necessary. Finally, defining this interface allows custom filesystem implementations to be supported seamlessly.

### What changes are included in this PR?

An initial sketch of a registry, with documentation as if the registry were complete to illustrate intended usage.

### Are these changes tested?

A toy module is added and a single unit test too.

### Are there any user-facing changes?

Users would be able to add their own filesystem implementations to the registry

* Closes: #38309

Authored-by: Benjamin Kietzman <bengilgit@gmail.com>
Signed-off-by: Benjamin Kietzman <bengilgit@gmail.com>
52 files changed
tree: e94d7856956e69dd0e9782307a6ef1ad2f9c222e
  1. .github/
  2. c_glib/
  3. ci/
  4. cpp/
  5. csharp/
  6. dev/
  7. docs/
  8. format/
  9. go/
  10. java/
  11. js/
  12. matlab/
  13. python/
  14. r/
  15. ruby/
  16. swift/
  17. testing
  18. .asf.yaml
  19. .clang-format
  20. .clang-tidy
  21. .clang-tidy-ignore
  22. .dir-locals.el
  23. .dockerignore
  24. .env
  25. .gitattributes
  26. .gitignore
  27. .gitmodules
  28. .hadolint.yaml
  29. .pre-commit-config.yaml
  30. .readthedocs.yml
  31. appveyor.yml
  32. CHANGELOG.md
  33. cmake-format.py
  34. CODE_OF_CONDUCT.md
  35. CONTRIBUTING.md
  36. docker-compose.yml
  37. header
  38. LICENSE.txt
  39. NOTICE.txt
  40. README.md
README.md

Apache Arrow

Fuzzing Status License Twitter Follow

Powering In-Memory Analytics

Apache Arrow is a development platform for in-memory analytics. It contains a set of technologies that enable big data systems to process and move data fast.

Major components of the project include:

Arrow is an Apache Software Foundation project. Learn more at arrow.apache.org.

What's in the Arrow libraries?

The reference Arrow libraries contain many distinct software components:

  • Columnar vector and table-like containers (similar to data frames) supporting flat or nested types
  • Fast, language agnostic metadata messaging layer (using Google's Flatbuffers library)
  • Reference-counted off-heap buffer memory management, for zero-copy memory sharing and handling memory-mapped files
  • IO interfaces to local and remote filesystems
  • Self-describing binary wire formats (streaming and batch/file-like) for remote procedure calls (RPC) and interprocess communication (IPC)
  • Integration tests for verifying binary compatibility between the implementations (e.g. sending data from Java to C++)
  • Conversions to and from other in-memory data structures
  • Readers and writers for various widely-used file formats (such as Parquet, CSV)

Implementation status

The official Arrow libraries in this repository are in different stages of implementing the Arrow format and related features. See our current feature matrix on git main.

How to Contribute

Please read our latest project contribution guide.

Getting involved

Even if you do not plan to contribute to Apache Arrow itself or Arrow integrations in other projects, we'd be happy to have you involved: