Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update documentation to add Databricks 12.2 as a supported platform [skip ci] #8830

Merged
merged 3 commits into from
Jul 28, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions docs/additional-functionality/delta-lake-support.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,13 +17,14 @@ This document details the Delta Lake features that are supported.

Delta Lake scans of the underlying Parquet files are presented in the query as normal Parquet
reads, so the Parquet reads will be accelerated in the same way raw Parquet file reads are
accelerated.
accelerated. Reads against tables that have deletion vectors enabled will fallback to the CPU.

### Metadata Queries

Reads of Delta Lake metadata, i.e.: the Delta log detailing the history of snapshots, will not
be GPU accelerated. The CPU will continue to process metadata queries on Delta Lake tables.


## Writing Delta Lake Tables

Delta Lake write acceleration is enabled by default. To disable acceleration of Delta Lake
Expand All @@ -38,6 +39,7 @@ Delta Lake writes:
- Delta Lake version 2.4.0 on Apache Spark 3.4.x
- Delta Lake on Databricks 10.4 LTS
- Delta Lake on Databricks 11.3 LTS
- Delta Lake on Databricks 12.2 LTS

Delta Lake writes will not be accelerated on Spark 3.1.x or earlier.

Expand All @@ -49,7 +51,8 @@ operation which is typically triggered via the DataFrame `write` API, e.g.:
`data.write.format("delta").save(...)`.

Table creation from selection, table insertion from SQL, and table merges are not currently
GPU accelerated. These operations will fallback to the CPU.
GPU accelerated. These operations will fallback to the CPU. Writes against tables that have
deletion vectors enabled will also fallback to the CPU.
jlowe marked this conversation as resolved.
Show resolved Hide resolved

#### Automatic Optimization of Writes

Expand Down
1 change: 1 addition & 0 deletions docs/additional-functionality/rapids-shuffle.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,7 @@ in our plugin:
| 3.4.1 | com.nvidia.spark.rapids.spark341.RapidsShuffleManager |
| Databricks 10.4 | com.nvidia.spark.rapids.spark321db.RapidsShuffleManager |
| Databricks 11.3 | com.nvidia.spark.rapids.spark330db.RapidsShuffleManager |
| Databricks 12.2 | com.nvidia.spark.rapids.spark332db.RapidsShuffleManager |

## Multi-Threaded Mode

Expand Down