Skip to content

Query produces different results after physical plan round trip to bytes #14253

@robtandy

Description

@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

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions