Github user DonnyZone commented on the issue:
https://github.com/apache/spark/pull/19559
@hvanhovell Yes! I made something wrong. The `timeFunctionCall` has
conflicts with `columnReference`. This fix will break every use of
CURRENT_DATE/CURRENT_TIMESTAMP.
For [SPARK-16836](https://github.com/apache/spark/pull/14442),
I think this feature should be implemented in analysis phase rather than in
parser phase. When there is no such columns, they can be transformed as
functions. Another approach is to define a configuration.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
