Github user rdblue commented on the issue:
https://github.com/apache/spark/pull/21230
So it was the use of `transformUp` that caused this rules to match multiple
times, right? In that case, would it make more sense to do what @marmbrus
suggested in the immutable plan PR and make this a strategy instead of an
optimizer rule?
That approach fits with what I suggested on #21118. We could have the scan
node handle the filter and the projection so that it doesn't matter whether the
source produces `UnsafeRow` or `InternalRow`.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
