olaky commented on PR #36753:
URL: https://github.com/apache/spark/pull/36753#issuecomment-1150993743
And for 3.0 we have: https://github.com/apache/spark/pull/36822 (looks to me
like there is an infrastructure problem with building it)
--
This is an automated message from the Apache Git
olaky commented on PR #36753:
URL: https://github.com/apache/spark/pull/36753#issuecomment-1150797803
Transforming with subqueries comes from
https://github.com/apache/spark/commit/1a356858577aa13012f56fdd4b41f8ea6fe230ce
and pruning comes from
olaky commented on PR #36753:
URL: https://github.com/apache/spark/pull/36753#issuecomment-1150242302
@MaxGekk 3.1 already does not have any transform with subqueries function,
so I would have to backport this as well. I personally feel that this could be
a risky endeavour not worth doing
olaky commented on PR #36753:
URL: https://github.com/apache/spark/pull/36753#issuecomment-1149853529
@MaxGekk since you closed this, should I still work on propagating this to
3.1 and 3.0? And how should we deal with the test failures happening on
branch-3.2?
--
This is an automated
olaky commented on PR #36753:
URL: https://github.com/apache/spark/pull/36753#issuecomment-1148633785
Merging is blocked because of a test failure that also surfaces in
https://github.com/apache/spark/pull/36386
--
This is an automated message from the Apache Git Service.
To respond to
olaky commented on PR #36753:
URL: https://github.com/apache/spark/pull/36753#issuecomment-1148258363
I cherry-picked 583a9c75bbb35387169d4f0cf763ef566d899954
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
