Github user viirya commented on the issue:
https://github.com/apache/spark/pull/18779
@maropu I have a PR before to solve that. Due to some reasons it will be
merged on 2.3. I am out of laptop, will refer it once I can access laptop.
On Aug 3, 2017 5:07 PM, "Takeshi Yamamuro" <notificati...@github.com> wrote:
@gatorsmile <https://github.com/gatorsmile> @viirya
<https://github.com/viirya> I looked into why it applied some analyzer
rules into already-analyzed plans and I noticed that some rules used
transform/transformUp instead of resolveOperators in apply.
SubstituteUnresolvedOrdinals also doesn't use resolveOperators, so the rule
is applied again into an already-analyzed plan master...maropu:SPARK-21580-3
<https://github.com/apache/spark/compare/master...maropu:SPARK-21580-3>.
â
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/apache/spark/pull/18779#issuecomment-319912782>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAEM9yUL3COM_lTj2xv-G-LYkO7w3Ffbks5sUY3egaJpZM4On4V0>
.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
