Github user maropu commented on the issue:
https://github.com/apache/spark/pull/21764
Do you have concrete usecases in your business? Basically, I think the
optimizer is a black-box for most users and they don't easily understand how it
works correctly when excluding some rules. Are there other database-like
systems that implement this kind of interfaces?
Even in debugging uses, is it not enough to define an individual test
optimizer for each debuggin use?, e.g.,
https://github.com/apache/spark/blob/e1de34113e057707dfc5ff54a8109b3ec7c16dfb/sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/ColumnPruningSuite.scala#L33?
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
