.. Licensed to the Apache Software Foundation (ASF) under one
.. or more contributor license agreements.  See the NOTICE file
.. distributed with this work for additional information
.. regarding copyright ownership.  The ASF licenses this file
.. to you under the Apache License, Version 2.0 (the
.. "License"); you may not use this file except in compliance
.. with the License.  You may obtain a copy of the License at

..   http://www.apache.org/licenses/LICENSE-2.0

.. Unless required by applicable law or agreed to in writing,
.. software distributed under the License is distributed on an
.. "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
.. KIND, either express or implied.  See the License for the
.. specific language governing permissions and limitations
.. under the License.

.. _filesystem:

.. currentmodule:: pyarrow.fs

Filesystem Interface
====================

PyArrow comes with an abstract filesystem interface, as well as concrete
implementations for various storage types.

The filesystem interface provides input and output streams as well as
directory operations.  A simplified view of the underlying data
storage is exposed.  Data paths are represented as *abstract paths*, which
are ``/``-separated, even on Windows, and shouldn't include special path
components such as ``.`` and ``..``.  Symbolic links, if supported by the
underlying storage, are automatically dereferenced.  Only basic
:class:`metadata <FileInfo>` about file entries, such as the file size
and modification time, is made available.

The core interface is represented by the base class :class:`FileSystem`.

Pyarrow implements natively the following filesystem subclasses:

* :ref:`filesystem-localfs` (:class:`LocalFileSystem`)
* :ref:`filesystem-s3` (:class:`S3FileSystem`)
* :ref:`filesystem-gcs` (:class:`GcsFileSystem`)
* :ref:`filesystem-hdfs` (:class:`HadoopFileSystem`)
* :ref:`filesystem-azurefs` (:class:`AzureFileSystem`)

It is also possible to use your own fsspec-compliant filesystem with pyarrow functionalities as described in the section :ref:`filesystem-fsspec`.


.. _filesystem-usage:

Usage
-----

Instantiating a filesystem
~~~~~~~~~~~~~~~~~~~~~~~~~~

A FileSystem object can be created with one of the constructors (and check the
respective constructor for its options):

.. code-block:: python

   >>> from pyarrow import fs
   >>> import pyarrow as pa
   >>> local = fs.LocalFileSystem()

or alternatively inferred from a URI:

.. code-block:: python

   >>> s3, path = fs.FileSystem.from_uri("s3://my-bucket")  # doctest: +SKIP
   >>> s3  # doctest: +SKIP
   <pyarrow._s3fs.S3FileSystem at ...>
   >>> path  # doctest: +SKIP
   'my-bucket'


Reading and writing files
~~~~~~~~~~~~~~~~~~~~~~~~~

Several of the IO-related functions in PyArrow accept either a URI (and infer
the filesystem) or an explicit ``filesystem`` argument to specify the filesystem
to read or write from. For example, the :meth:`pyarrow.parquet.read_table`
function can be used in the following ways:

.. code-block:: python

   >>> import pyarrow.parquet as pq
   >>> # using a URI -> filesystem is inferred
   >>> pq.read_table("s3://my-bucket/data.parquet")  # doctest: +SKIP
   >>> # using a path and filesystem
   >>> s3 = fs.S3FileSystem(..)  # doctest: +SKIP
   >>> pq.read_table("my-bucket/data.parquet", filesystem=s3)  # doctest: +SKIP

The filesystem interface further allows to open files for reading (input) or
writing (output) directly, which can be combined with functions that work with
file-like objects. For example:

.. code-block:: python

   >>> table = pa.table({'col1': [1, 2, 3]})
   >>> local = fs.LocalFileSystem()
   >>> with local.open_output_stream("test.arrow") as file:
   ...    with pa.RecordBatchFileWriter(file, table.schema) as writer:
   ...       writer.write_table(table)


Listing files
~~~~~~~~~~~~~

Inspecting the directories and files on a filesystem can be done with the
:meth:`FileSystem.get_file_info` method. To list the contents of a directory,
use the :class:`FileSelector` object to specify the selection:

.. code-block:: python

   >>> local.get_file_info(fs.FileSelector("dataset/", recursive=True))  # doctest: +SKIP
   [<FileInfo for 'dataset/part=B': type=FileType.Directory>,
    <FileInfo for 'dataset/part=B/data0.parquet': type=FileType.File, size=1564>,
    <FileInfo for 'dataset/part=A': type=FileType.Directory>,
    <FileInfo for 'dataset/part=A/data0.parquet': type=FileType.File, size=1564>]

This returns a list of :class:`FileInfo` objects, containing information about
the type (file or directory), the size, the date last modified, etc.

You can also get this information for a single explicit path (or list of
paths):

.. code-block:: python

   >>> local.get_file_info('test.arrow')
   <FileInfo for 'test.arrow': type=FileType.File, size=498>
   >>> local.get_file_info('non_existent')
   <FileInfo for 'non_existent': type=FileType.NotFound>


.. _filesystem-localfs:

Local FS
--------

The :class:`LocalFileSystem` allows you to access files on the local machine.

Example how to write to disk and read it back:

.. code-block:: python

   >>> local = fs.LocalFileSystem()
   >>> with local.open_output_stream('pyarrowtest.dat') as stream:
   ...     stream.write(b'data')
   4
   >>> with local.open_input_stream('pyarrowtest.dat') as stream:
   ...     print(stream.readall())
   b'data'


.. _filesystem-s3:

S3
--

PyArrow implements natively a S3 filesystem for S3 compatible storage.

The :class:`S3FileSystem` constructor has several options to configure the S3
connection (e.g. credentials, the region, an endpoint override, etc). In
addition, the constructor will also inspect configured S3 credentials as
supported by AWS (such as the ``AWS_ACCESS_KEY_ID`` and
``AWS_SECRET_ACCESS_KEY`` environment variables, AWS configuration files,
and EC2 Instance Metadata Service for EC2 nodes).


Example how you can read contents from a S3 bucket:

.. code-block:: python

   >>> s3 = fs.S3FileSystem(region='eu-west-3')  # doctest: +SKIP
   >>> # List all contents in a bucket, recursively
   >>> s3.get_file_info(fs.FileSelector('my-test-bucket', recursive=True))  # doctest: +SKIP
   [<FileInfo for 'my-test-bucket/File1': type=FileType.File, size=10>,
    <FileInfo for 'my-test-bucket/File5': type=FileType.File, size=10>,
    <FileInfo for 'my-test-bucket/Dir1': type=FileType.Directory>,
    <FileInfo for 'my-test-bucket/Dir2': type=FileType.Directory>,
    <FileInfo for 'my-test-bucket/EmptyDir': type=FileType.Directory>,
    <FileInfo for 'my-test-bucket/Dir1/File2': type=FileType.File, size=11>,
    <FileInfo for 'my-test-bucket/Dir1/Subdir': type=FileType.Directory>,
    <FileInfo for 'my-test-bucket/Dir2/Subdir': type=FileType.Directory>,
    <FileInfo for 'my-test-bucket/Dir2/Subdir/File3': type=FileType.File, size=10>]
   >>> # Open a file for reading and download its contents
   >>> f = s3.open_input_stream('my-test-bucket/Dir1/File2')  # doctest: +SKIP
   >>> f.readall()  # doctest: +SKIP
   b'some data'


Note that it is important to configure :class:`S3FileSystem` with the correct
region for the bucket being used. If ``region`` is not set, the AWS SDK will
choose a value, defaulting to 'us-east-1' if the SDK version is <1.8.
Otherwise it will try to use a variety of heuristics (environment variables,
configuration profile, EC2 metadata server) to resolve the region.

It is also possible to resolve the region from the bucket name for
:class:`S3FileSystem` by using :func:`pyarrow.fs.resolve_s3_region` or
:func:`pyarrow.fs.S3FileSystem.from_uri`.

Here are a couple examples in code:

.. code-block:: python

   >>> s3 = fs.S3FileSystem(region=fs.resolve_s3_region('my-test-bucket'))  # doctest: +SKIP
   >>> # Or via URI:
   >>> s3, path = fs.S3FileSystem.from_uri('s3://[access_key:secret_key@]bucket/path]')  # doctest: +SKIP


.. seealso::

   See the `AWS docs <https://docs.aws.amazon.com/sdk-for-cpp/v1/developer-guide/credentials.html>`__
   for the different ways to configure the AWS credentials.

   :func:`pyarrow.fs.resolve_s3_region` for resolving region from a bucket name.

Troubleshooting
~~~~~~~~~~~~~~~

When using :class:`S3FileSystem`, output is only produced for fatal errors or
when printing return values. For troubleshooting, the log level can be set using
the environment variable ``ARROW_S3_LOG_LEVEL``. The log level must be set prior
to running any code that interacts with S3. Possible values include ``FATAL`` (the
default), ``ERROR``, ``WARN``, ``INFO``, ``DEBUG`` (recommended), ``TRACE``, and ``OFF``.

.. _filesystem-gcs:

Google Cloud Storage File System
--------------------------------

PyArrow implements natively a Google Cloud Storage (GCS) backed file system
for GCS storage.

If not running on Google Cloud Platform (GCP), this generally requires the
environment variable ``GOOGLE_APPLICATION_CREDENTIALS`` to point to a
JSON file containing credentials. Alternatively, use the ``gcloud`` CLI to
generate a credentials file in the default location::

   gcloud auth application-default login

To connect to a public bucket without using any credentials, you must pass
``anonymous=True`` to :class:`GcsFileSystem`. Otherwise, the filesystem
will report ``Couldn't resolve host name`` since there are different host
names for authenticated and public access.

Example showing how you can read contents from a GCS bucket:

.. code-block:: python

   >>> from datetime import timedelta
   >>> gcs = fs.GcsFileSystem(anonymous=True, retry_time_limit=timedelta(seconds=15))  # doctest: +SKIP
   >>> # List all contents in a bucket, recursively
   >>> uri = "gcp-public-data-landsat/LC08/01/001/003/"  # doctest: +SKIP
   >>> file_list = gcs.get_file_info(fs.FileSelector(uri, recursive=True))  # doctest: +SKIP
   >>> # Open a file for reading and download its contents
   >>> f = gcs.open_input_stream(file_list[0].path)  # doctest: +SKIP
   >>> f.read(64)  # doctest: +SKIP
   b'GROUP = FILE_HEADER\n  LANDSAT_SCENE_ID = "LC80010032013082LGN03"\n  S'

.. seealso::

   The :class:`GcsFileSystem` constructor by default uses the
   process described in `GCS docs <https://google.aip.dev/auth/4110>`__
   to resolve credentials.


.. _filesystem-hdfs:

Hadoop Distributed File System (HDFS)
-------------------------------------

PyArrow comes with bindings to the Hadoop File System (based on C++ bindings
using ``libhdfs``, a JNI-based interface to the Java Hadoop client). You connect
using the :class:`HadoopFileSystem` constructor:

.. code-block:: python

   >>> hdfs = fs.HadoopFileSystem(host, port, user=user, kerb_ticket=ticket_cache_path)  # doctest: +SKIP

The ``libhdfs`` library is loaded **at runtime** (rather than at link / library
load time, since the library may not be in your LD_LIBRARY_PATH), and relies on
some environment variables.

* ``HADOOP_HOME``: the root of your installed Hadoop distribution. Often has
  ``lib/native/libhdfs.so``.

* ``JAVA_HOME``: the location of your Java SDK installation.

* ``ARROW_LIBHDFS_DIR`` (optional): explicit location of ``libhdfs.so`` if it is
  installed somewhere other than ``$HADOOP_HOME/lib/native``.

* ``CLASSPATH``: must contain the Hadoop jars. You can set these using:

  .. code-block:: shell

      >>> export CLASSPATH=`$HADOOP_HOME/bin/hadoop classpath --glob`  # doctest: +SKIP
      >>> # or on Windows
      >>> %HADOOP_HOME%/bin/hadoop classpath --glob > %CLASSPATH%  # doctest: +SKIP

  In contrast to the legacy HDFS filesystem with ``pa.hdfs.connect``, setting
  ``CLASSPATH`` is not optional (pyarrow will not attempt to infer it).

.. _filesystem-azurefs:

Azure Storage File System
-------------------------

PyArrow implements natively an Azure filesystem for Azure Blob Storage with or
without heirarchical namespace enabled.

The :class:`AzureFileSystem` constructor has several options to configure the
Azure Blob Storage connection (e.g. account name, account key, SAS token, etc.).

If neither ``account_key`` or ``sas_token`` is specified a `DefaultAzureCredential <https://github.com/Azure/azure-sdk-for-cpp/blob/main/sdk/identity/azure-identity/README.md#defaultazurecredential>`__
is used for authentication. This means it will try several types of authentication
and go with the first one that works. If any authentication parameters are provided when
initialising the FileSystem, they will be used instead of the default credential.

Example showing how you can read contents from an Azure Blob Storage account:

.. code-block:: python

   >>> azure_fs = fs.AzureFileSystem(account_name='myaccount')  # doctest: +SKIP
   >>> # List all contents in a container, recursively
   >>> azure_fs.get_file_info(fs.FileSelector('my-container', recursive=True))  # doctest: +SKIP
   [<FileInfo for 'my-container/File1': type=FileType.File, size=10>,
    <FileInfo for 'my-container/File2': type=FileType.File, size=20>,
    <FileInfo for 'my-container/Dir1': type=FileType.Directory>,
    <FileInfo for 'my-container/Dir1/File3': type=FileType.File, size=30>]
   >>> # Open a file for reading and download its contents
   >>> f = azure_fs.open_input_stream('my-container/File1')  # doctest: +SKIP
   >>> f.readall()  # doctest: +SKIP
   b'some data'

For more details on the parameters and usage, refer to the :class:`AzureFileSystem` class documentation.

.. seealso::

   See the `Azure SDK for C++ documentation <https://github.com/Azure/azure-sdk-for-cpp>`__
   for more information on authentication and configuration options.

.. _filesystem-fsspec:

Using fsspec-compatible filesystems with Arrow
----------------------------------------------

The filesystems mentioned above are natively supported by Arrow C++ / PyArrow.
The Python ecosystem, however, also has several filesystem packages. Those
packages following the `fsspec`_ interface can be used in PyArrow as well.

Functions accepting a filesystem object will also accept an fsspec subclass.
For example:

.. code-block:: python

   >>> # creating an fsspec-based filesystem object for Google Cloud Storage
   >>> import gcsfs  # doctest: +SKIP
   >>> fs_gcs = gcsfs.GCSFileSystem(project='my-google-project')  # doctest: +SKIP
   >>> # using this to read a partitioned dataset
   >>> import pyarrow.dataset as ds  # doctest: +SKIP
   >>> ds.dataset("data/", filesystem=fs_gcs)  # doctest: +SKIP

Similarly for Azure Blob Storage:

.. code-block:: python

   >>> import adlfs  # doctest: +SKIP
   >>> # ... load your credentials and configure the filesystem
   >>> fs_azure = adlfs.AzureBlobFileSystem(account_name=account_name, account_key=account_key)  # doctest: +SKIP
   >>> ds.dataset("mycontainer/data/", filesystem=fs_azure)  # doctest: +SKIP

Under the hood, the fsspec filesystem object is wrapped into a python-based
PyArrow filesystem (:class:`PyFileSystem`) using :class:`FSSpecHandler`.
You can also manually do this to get an object with the PyArrow FileSystem
interface:

.. code-block:: python

   >>> from pyarrow.fs import PyFileSystem, FSSpecHandler  # doctest: +SKIP
   >>> pa_fs = PyFileSystem(FSSpecHandler(fs_azure))  # doctest: +SKIP

Then all the functionalities of :class:`FileSystem` are accessible:

.. code-block:: python

   >>> # write data
   >>> with pa_fs.open_output_stream('mycontainer/pyarrowtest.dat') as stream:  # doctest: +SKIP
   ...    stream.write(b'data')
   >>> # read data
   >>> with pa_fs.open_input_stream('mycontainer/pyarrowtest.dat') as stream:  # doctest: +SKIP
   ...    print(stream.readall())
   b'data'
   >>> # read a partitioned dataset
   >>> ds.dataset("data/", filesystem=pa_fs)  # doctest: +SKIP


Using fsspec-compatible filesystem URIs
---------------------------------------

PyArrow can automatically instantiate fsspec filesystems by prefixing the URI
scheme with ``fsspec+``. This allows you to use the fsspec-compatible
filesystems directly with PyArrow's IO functions without needing to manually
create a filesystem object. Example writing and reading a Parquet file
using an in-memory filesystem provided by `fsspec`_:

.. code-block:: python

   >>> table = pa.table({'a': [1, 2, 3]})
   >>> pq.write_table(table, "fsspec+memory://path/to/my_table.parquet")  # doctest: +SKIP
   >>> pq.read_table("fsspec+memory://path/to/my_table.parquet")  # doctest: +SKIP

Example reading parquet file from GitHub directly:

.. code-block:: python

   >>> pq.read_table("fsspec+github://apache:arrow-testing@/data/parquet/alltypes-java.parquet")  # doctest: +SKIP

Hugging Face URIs are explicitly allowed as a shortcut without needing to prefix
with ``fsspec+``. This is useful for reading datasets hosted on Hugging Face:

.. code-block:: python

   >>> pq.read_table("hf://datasets/stanfordnlp/imdb/plain_text/train-00000-of-00001.parquet")  # doctest: +SKIP


Using Arrow filesystems with fsspec
-----------------------------------

The Arrow FileSystem interface has a limited, developer-oriented API surface.
This is sufficient for basic interactions and for using this with
Arrow's IO functionality. On the other hand, the `fsspec`_ interface provides
a very large API with many helper methods. If you want to use those, or if you
need to interact with a package that expects fsspec-compatible filesystem
objects, you can wrap an Arrow FileSystem object with fsspec.

Starting with ``fsspec`` version 2021.09, the ``ArrowFSWrapper`` can be used
for this:

.. code-block:: python

   >>> local = fs.LocalFileSystem()
   >>> from fsspec.implementations.arrow import ArrowFSWrapper  # doctest: +SKIP
   >>> local_fsspec = ArrowFSWrapper(local)  # doctest: +SKIP

The resulting object now has an fsspec-compatible interface, while being backed
by the Arrow FileSystem under the hood.
Example usage to create a directory and file, and list the content:

.. code-block:: python

   >>> local_fsspec.mkdir("./test")  # doctest: +SKIP
   >>> local_fsspec.touch("./test/file.txt")  # doctest: +SKIP
   >>> local_fsspec.ls("./test/")  # doctest: +SKIP
   ['./test/file.txt']

For more information, see the `fsspec`_ documentation.


.. _fsspec: https://filesystem-spec.readthedocs.io/en/latest/