-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Map vs List contains/is_in behavior #29311
Copy link
Copy link
Open
Labels
A-dtypeArea: data types in generalArea: data types in generalA-dtype-list/arrayArea: list/array data typeArea: list/array data typeA-dtype-mapArea: map data typeArea: map data typeA-planArea: logical plan and intermediate representationArea: logical plan and intermediate representationA-typingArea: type checkingArea: type checkingbugSomething isn't workingSomething isn't working
Description
Activity
Metadata
Metadata
Assignees
Labels
A-dtypeArea: data types in generalArea: data types in generalA-dtype-list/arrayArea: list/array data typeArea: list/array data typeA-dtype-mapArea: map data typeArea: map data typeA-planArea: logical plan and intermediate representationArea: logical plan and intermediate representationA-typingArea: type checkingArea: type checkingbugSomething isn't workingSomething isn't working
In #29296 we uncovered some mismatches between how
.containsand.is_inwork betweenMapandList(andArray). I believe thatMaphandles all of these correctly,Listdiffers in a couple of places due to legacy behavior, but also due to allowing innernulls.Investigate all differences here, related to mixed type keys, and keys of the same type but parameterized differently (different int width, float width, temporal resolution, time zone, decimal precision/scale,...)