David Sisson

This establishes the physical mark join relation. It utilizes a mark (a nullable boolean field reference) to reduce the amount of data that needs to be processed.

This defines the physical delimiter join relation. It utilizes duplicate elimination to reduce the size of one side and then performs multiple scans on the other side to reduce the...

Add support for NOT IN SUBQUERY

2

The subquery type InPredicate supports IN but it does not support NOT IN which is used in some anti-join implementations.

When a map contains the same key multiple times there are a few options for the potential behavior: 1. Always choose the last value for that map key (as if...

Defines the Mark Join used by a number of engines in query rewrites.

Project relation: do we always need to just add columns?

2

Project relations are currently defined as adding columns to our output. Two Substrait implementations do not implement project relations this way (DuckDB and Datafusion) and the semantics of the plan...

Projects from Substrait do not include input fields as output fields

2

### Describe the bug According to the [Substrait specification](https://substrait.io/relations/logical_relations/#project-operation) project relations emit all if the input fields followed by the list of new expressions. Datafusion only emits the new expressions....