Github user mallman commented on the issue:
https://github.com/apache/spark/pull/21320
> @mallman I still think we need to split it to two PRs. To resolve the
issues you mentioned above, how about creating a separate PR? Only 10 days left
before the code freeze of Spark 2.4. We plan to merge the main logic of nested
column pruning to Spark 2.4 release first and then address the other parts in
the next release. WDYT?
I've rebased and pushed a commit that removes the changes to
`ParquetReadSupport.scala` and `ParquetFileFormat.scala`. I've also marked
failing tests in `ParquetSchemaPruningSuite.scala` as ignored. Is this what you
had in mind?
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
