Query produces different results after physical plan round trip to bytes

[robtandy]

Describe the bug

Serializing a physical plan to bytes and then recreating it produces a different output. This was observed on TPCH query 3.

Note though, that it was also observed that if you remove the config option: datafusion.execution.parquet.pushdown_filters the discrepancy goes away.

I'll work up a PR to improve the round trip tests to hopefully isolate the problem.

To Reproduce

A reproducible example is here
https://github.com/robtandy/datafusion-physical-plan-round-trip/blob/main/src/main.rs

Expected behavior

Physical plans should produce the same output after a round trip to proto and back.

Additional context

No response

[alamb]

This certainly sounds not good (and an excellent find)

[alamb]

Added to the list of things to look at before release on

• Release DataFusion 45.0.0 #14008

[blaginin]

Looks like the way we serialize pushdown_filters is wrong. It's true in the initial struct but false after deserialization

[blaginin]

take