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

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

Merged
merged 4 commits into from
May 2, 2022
Merged
Changes from 1 commit
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
14 changes: 13 additions & 1 deletion docs/get-started/getting-started-databricks.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,19 @@ 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.

Below 2 rebase mode related Spark configurations are set to `LEGACY` by default on Databricks:
viadea marked this conversation as resolved.
Show resolved Hide resolved

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

It will cause CPU fallback when writing parquet files. If you do not need "LEGACY" mode, please
set them back to "EXCEPTION" which is the default value in Apache Spark.
viadea marked this conversation as resolved.
Show resolved Hide resolved

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