Skip to content

DPP fallback not working correct in awslabs TPC-DS benchmark #3870

@andygrove

Description

@andygrove

Describe the bug

In the awslabs benchmark, some scans in q25 fell back to Spark because the scans use DPP. This is expected behavior. However, the fallback somehow changed the Spark plan, removing DPP, causing the scan to read all partitions, resulting in dramatic regression.

Steps to reproduce

No response

Expected behavior

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions