Skip to content
This repository was archived by the owner on Jan 7, 2025. It is now read-only.

Tracking: Which TPC-H queries can be run? #184

@jurplel

Description

@jurplel

Related: #11, #68, #127

Ran with no datafusion optimizations (all of our own optimizations)

Tests were done for whether or not the query works with perfbench. Query result may be incorrect, but it compiles and runs

  • Q1
  • Q2
    • Plan generated is so bad that it causes an overflow in datafusion's cardinality estimation
  • Q3
  • Q4
    • Depends on subquery unnesting EXISTS support
  • Q5
  • Q6
  • Q7
  • Q8
  • Q9
  • Q10
  • Q11
    • Bug: test panicked: Column index 2 out of bounds 2 + 0
  • Q12
  • Q13
  • Q14
  • Q15
  • Q16
    • Depends on subquery unnesting IN support
    • May depend also on left anti join
  • Q17
    • Bug: test panicked: assertion failed: i + left_schema_size < left_schema_size + right_schema_size
  • Q18
    • Depends on subquery unnesting IN support
    • May depend also on left semi join
  • Q19
  • Q20
    • Depends on subquery unnesting IN support
    • May depend also on left semi join
  • Q21
    • Depends on subquery unnesting EXISTS support
    • May depend also on left semi and left anti join
  • Q22
    • Depends on subquery unnesting IN and EXISTS support
    • May depend also on left anti join

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions