-
Notifications
You must be signed in to change notification settings - Fork 236
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
[WIP] Orc writes don't fully support Booleans with nulls #11763
base: branch-24.12
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1243,6 +1243,14 @@ val GPU_COREDUMP_PIPE_PATTERN = conf("spark.rapids.gpu.coreDump.pipePattern") | |
.booleanConf | ||
.createWithDefault(true) | ||
|
||
val ENABLE_ORC_NULLABLE_BOOL = conf("spark.rapids.sql.format.orc.write.boolType.enabled") | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can we just fall back for all booleans instead of only nullable ones? Spark already marks almost everything as nullable, so there is very little value in trying to distinguish between the two. But then I see things like #11762 where it scares me that CUDF might end up writing something out that they think is valid, but in practice is not. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ack. yes. |
||
.doc("When set to false disables nullable boolean columns for ORC writes." + | ||
"Set to true if your data does not have null booleans and want tp experiment" + | ||
"See https://github.com/NVIDIA/spark-rapids/issues/11736.") | ||
.internal() | ||
.booleanConf | ||
.createWithDefault(false) | ||
|
||
val ENABLE_EXPAND_PREPROJECT = conf("spark.rapids.sql.expandPreproject.enabled") | ||
.doc("When set to false disables the pre-projection for GPU Expand. " + | ||
"Pre-projection leverages the tiered projection to evaluate expressions that " + | ||
|
@@ -2964,6 +2972,8 @@ class RapidsConf(conf: Map[String, String]) extends Logging { | |
|
||
lazy val maxNumOrcFilesParallel: Int = get(ORC_MULTITHREAD_READ_MAX_NUM_FILES_PARALLEL) | ||
|
||
lazy val isOrcBoolNullTypeEnabled: Boolean = get(ENABLE_ORC_NULLABLE_BOOL) | ||
|
||
lazy val isCsvEnabled: Boolean = get(ENABLE_CSV) | ||
|
||
lazy val isCsvReadEnabled: Boolean = get(ENABLE_CSV_READ) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is removing the test for nullable boolean values. Can we have an explicit test(s) that have a non-nullable struct with nullable values, or many different types, in it? I am fine if this is a follow on issue.