We are still working on a reproduction but when we have a query similar to this one:
The table is partitioned and both sub queries will force a parquet pruning on the table. Because we share the parquet metadata object in ParquetGroupScan, the second query end up being "over pruned" and we get wrong results.
The plan doesn't show the problem.
|add unit test for DRILL-4449||Resolved|