[DOCS] Add user guide for read_sql

daft/io/_sql.py

@@ -23,7 +23,7 @@ def read_sql(
     num_partitions: Optional[int] = None,
     disable_pushdowns_to_sql: bool = False,
 ) -> DataFrame:
-    """Creates a DataFrame from the results of a SQL query.
+    """Create a DataFrame from the results of a SQL query.
 
     Args:
         sql (str): SQL query to execute
@@ -37,8 +37,8 @@ def read_sql(
         DataFrame: Dataframe containing the results of the query
 
     .. NOTE::
-        #. Supported databases:
-            Daft uses `SQLGlot <https://sqlglot.com/sqlglot/dialects.html>`_ to build SQL queries, so it supports all databases that SQLGlot supports.
+        #. Supported dialects:
+            Daft uses `SQLGlot <https://sqlglot.com/sqlglot.html>`_ to build and translate SQL queries between dialects. For a list of supported dialects, see `SQLGlot's dialect documentation <https://sqlglot.com/sqlglot/dialects.html>`_.
 
         #. Partitioning:
             When `partition_col` is specified, the function partitions the query based on that column.

docs/source/user_guide/integrations.rst

@@ -9,3 +9,4 @@ Integrations
     integrations/hudi
     integrations/microsoft-azure
     integrations/aws
+    integrations/sql

docs/source/user_guide/integrations/sql.rst

@@ -0,0 +1,156 @@
+SQL
+===
+
+You can read the results of SQL queries from databases, data warehouses, and query engines, into a Daft DataFrame via the :func:`daft.read_sql` function.
+
+Daft currently supports:
+
+1. **20+ SQL Dialects:** Daft supports over 20 databases, data warehouses, and query engines by using `SQLGlot <https://sqlglot.com/sqlglot.html>`_ to convert SQL queries across dialects. See the full list of supported dialects `here <https://sqlglot.com/sqlglot/dialects.html>`__.
+2. **Parallel + Distributed Reads:** Daft parallelizes SQL reads by using all local machine cores with its default multithreading runner, or all cores across multiple machines if using the :ref:`distributed Ray runner <scaling_up>`.
+3. **Skipping Filtered Data:** Daft ensures that only data that matches your :meth:`df.select(...) <daft.DataFrame.select>`, :meth:`df.limit(...) <daft.DataFrame.limit>`, and :meth:`df.where(...) <daft.DataFrame.where>` expressions will be read, often skipping entire partitions/columns.
+
+Installing Daft with SQL Support
+********************************
+
+Install Daft with the ``getdaft[sql]`` extra, or manually install the required packages: `ConnectorX <https://sfu-db.github.io/connector-x/databases.html>`__, `SQLAlchemy <https://docs.sqlalchemy.org/en/20/orm/quickstart.html>`__, and `SQLGlot <https://sqlglot.com/sqlglot.html>`__.
+
+.. code-block:: shell
+
+    pip install -U "getdaft[sql]"
+
+Reading a SQL query
+*******************
+
+To read a SQL query, provide :func:`daft.read_sql` with the **SQL query** and a **URL** for the data source.
+
+The example below creates a local SQLite table for Daft to read.
+
+.. code:: python
+
+    import sqlite3
+
+    connection = sqlite3.connect("example.db")
+    connection.execute(
+        "CREATE TABLE IF NOT EXISTS books (title TEXT, author TEXT, year INTEGER)"
+    )
+    connection.execute(
+        """
+    INSERT INTO books (title, author, year)
+    VALUES
+        ('The Great Gatsby', 'F. Scott Fitzgerald', 1925),
+        ('To Kill a Mockingbird', 'Harper Lee', 1960),
+        ('1984', 'George Orwell', 1949),
+        ('The Catcher in the Rye', 'J.D. Salinger', 1951)
+    """
+    )
+    connection.commit()
+    connection.close()
+
+After writing this local example table, we can easily read it into a Daft DataFrame.
+
+.. code:: python
+
+    # Read SQL query into Daft DataFrame
+    import daft
+
+    df = daft.read_sql(
+        "SELECT * FROM books",
+        "sqlite:///example.db",
+    )
+
+Daft uses `ConnectorX <https://sfu-db.github.io/connector-x/databases.html>`_ under the hood to read SQL data. ConnectorX is a fast, Rust based SQL connector that reads directly into Arrow Tables, enabling zero-copy transfer into Daft dataframes.
+If the database is not supported by ConnectorX (list of supported databases `here <https://sfu-db.github.io/connector-x/intro.html#supported-sources-destinations>`__), Daft will fall back to using `SQLAlchemy <https://docs.sqlalchemy.org/en/20/orm/quickstart.html>`__.
+
+You can also directly provide a SQL alchemy connection via a **connection factory**. This way, you have the flexibility to provide additional parameters to the engine.
+
+.. code:: python
+
+    # Read SQL query into Daft DataFrame using a connection factory
+    import daft
+    from sqlalchemy import create_engine
+
+    def create_connection():
+        return sqlalchemy.create_engine("sqlite:///example.db", echo=True).connect()
+
+    df = daft.read_sql("SELECT * FROM books", create_connection)
+
+Parallel + Distributed Reads
+****************************
+
+For large datasets, Daft can parallelize SQL reads by using all local machine cores with its default multithreading runner, or all cores across multiple machines if using the :ref:`distributed Ray runner <scaling_up>`.
+
+Supply the :meth:`daft.read_sql` function with a **partition column** and optionally the **number of partitions** to enable parallel reads.
+
+.. code:: python
+
+    # Read SQL query into Daft DataFrame with parallel reads
+    import daft
+
+    df = daft.read_sql(
+        "SELECT * FROM table",
+        "sqlite:///big_table.db",
+        partition_on="col",
+        num_partitions=3,
+    )
+
+Behind the scenes, Daft will partition the data by appending a ``WHERE col > ... AND col <= ...`` clause to the SQL query, and then reading each partition in parallel.
+
+.. image:: /_static/sql_distributed_read.png
+    :width: 800px
+    :align: center
+
+Data Skipping Optimizations
+***************************
+
+Filter, projection, and limit pushdown optimizations can be used to reduce the amount of data read from the database.
+
+In the example below, Daft reads the top ranked terms from the BigQuery Google Trends dataset. The ``where`` and ``select`` expressions in this example will be pushed down into the SQL query itself, we can see this by calling the :meth:`df.explain() <daft.DataFrame.explain>` method.
+
+.. code:: python
+
+    import daft, sqlalchemy, datetime
+
+    def create_conn():
+        engine = sqlalchemy.create_engine(
+            "bigquery://", credentials_path="path/to/service_account_credentials.json"
+        )
+        return engine.connect()
+
+
+    df = daft.read_sql("SELECT * FROM `bigquery-public-data.google_trends.top_terms`", create_conn)
+
+    df = df.where((df["refresh_date"] >= datetime.date(2024, 4, 1)) & (df["refresh_date"] < datetime.date(2024, 4, 8)))
+    df = df.where(df["rank"] == 1)
+    df = df.select(df["refresh_date"].alias("Day"), df["term"].alias("Top Search Term"), df["rank"])
+    df = df.distinct()
+    df = df.sort(df["Day"], desc=True)
+
+    df.explain(show_all=True)
+
+    # Output
+    # ..
+    # == Physical Plan ==
+    # ..
+    # |   SQL Query = SELECT refresh_date, term, rank FROM
+    #  (SELECT * FROM `bigquery-public-data.google_trends.top_terms`)
+    #  AS subquery WHERE rank = 1 AND refresh_date >= CAST('2024-04-01' AS DATE)
+    #  AND refresh_date < CAST('2024-04-08' AS DATE)
+
+
+
+The second last line labeled 'SQL Query =' shows the query that Daft executed. Filters such as `rank = 1` and projections such as `SELECT refresh_date, term, rank` have been injected into the query.
+
+Without these pushdowns, Daft would execute the unmodified `SELECT * FROM 'bigquery-public-data.google_trends.top_terms'` query and read in the entire dataset/table. We tested the code above on Google Colab (12GB RAM):
+
+- With pushdowns, the code ran in **8.87s** with a peak memory of **315.97 MiB**
+- Without pushdowns, the code took over **2 mins** before crashing with an **out of memory** error.
+
+You could modify the SQL query to add the filters and projections yourself, but this may become lengthy and error-prone, particularly with many expressions. That's why Daft automatically handles it for you.
+
+Roadmap
+*******
+
+Here are the SQL features that are on our roadmap. Please let us know if you would like to see support for any of these features!
+
+1. Write support into SQL databases.
+2. Reads via `ADBC (Arrow Database Connectivity) <https://arrow.apache.org/docs/format/ADBC.html>`_.