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.

Sign up for GitHub

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

Jump to bottom

[DOC] Add rebase mode notes for databricks doc [skip ci] #5408

Merged
merged 4 commits into from
May 2, 2022
Merged

[DOC] Add rebase mode notes for databricks doc [skip ci] #5408

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
e81fc08
Add rebase mode notes for databricks doc
viadea Apr 29, 2022
169ac14
Update docs/get-started/getting-started-databricks.md
viadea Apr 30, 2022
8636a58
Update docs/get-started/getting-started-databricks.md
viadea Apr 30, 2022
9333535
Add spark 3.0 and higher
viadea Apr 30, 2022
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
15 changes: 14 additions & 1 deletion docs/get-started/getting-started-databricks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,20 @@ when using the plugin. Queries may still see significant speedups even with AQE
(where N is the number of GPUs per node). This will result in failed executors when starting the
cluster.

5. Databricks makes changes to the runtime without notification.
5. Parquet rebase mode is set to "LEGACY" by default.

The following Spark configurations are set to `LEGACY` by default on Databricks:

```
spark.sql.legacy.parquet.datetimeRebaseModeInWrite
spark.sql.legacy.parquet.int96RebaseModeInWrite
```

These settings will cause a CPU fallback for Parquet writes involving dates and timestamps.
If you do not need `LEGACY` write semantics, set these configs to `EXCEPTION` which is
the default value in Apache Spark 3.0 and higher.

6. Databricks makes changes to the runtime without notification.

Databricks makes changes to existing runtimes, applying patches, without notification.
[Issue-3098](https://github.com/NVIDIA/spark-rapids/issues/3098) is one example of this. We run
Expand Down