Github user sameeragarwal commented on a diff in the pull request:
https://github.com/apache/spark/pull/17186#discussion_r107803893
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/internal/SQLConf.scala ---
@@ -187,6 +187,15 @@ object SQLConf {
.booleanConf
.createWithDefault(false)
+ val CONSTRAINT_PROPAGATION_ENABLED =
buildConf("spark.sql.constraintPropagation.enabled")
+ .internal()
+ .doc("When true, the query optimizer will use constraint propagation
in query plans to " +
--- End diff --
nit: 'get around the issue' might sound pretty vague to a non-expert user.
How about something along these lines?
```scala
.doc("When true, the query optimizer will infer and propagate data
constraints in the query " +
"plan to optimize them. Constraint propagation can sometimes be
computationally expensive" +
"for certain kinds of query plans (such as those with a large number
of predicates and " +
"aliases) which might negatively impact overall runtime.")
```
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
