Skip to content

Commit 53cd54d

Browse files
viiryaIsaac
andcommitted
docs: only hashable NOT NULL tuple elements become equi-join keys
Co-authored-by: Isaac <[email protected]>
1 parent e3d0754 commit 53cd54d

1 file changed

Lines changed: 5 additions & 3 deletions

File tree

  • docs/source/library-user-guide/upgrading

‎docs/source/library-user-guide/upgrading/56.0.0.md‎

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -934,9 +934,11 @@ Wire compatibility is directional:
934934
### Null-aware joins record their `NOT IN` value key count
935935

936936
Multi-column `(a, b) NOT IN (SELECT x, y ...)` is now planned as a null-aware
937-
join. Its first equi-join keys are the tuple elements that can be NULL,
938-
followed by the elements that cannot and any correlation keys, so a null-aware
939-
join now records how many of its leading keys are `NOT IN` value keys:
937+
join. Its first equi-join keys are the tuple elements that can be NULL. The
938+
elements that cannot be NULL and any equality correlations follow as further
939+
equi-join keys when their types can be hashed, and otherwise stay in the join
940+
filter. A null-aware join therefore records how many of its leading keys are
941+
`NOT IN` value keys:
940942

941943
- `datafusion_expr::logical_plan::Join` has a new `null_aware_value_keys: usize`
942944
field.

0 commit comments

Comments
 (0)