[EPIC] A collection of issues for supporting the `MAP` DataType

[alamb]

Is your feature request related to a problem or challenge?

Arrow contains a MapArray

DataFusion has incomplete support for this type; This ticket tracks adding new fetures.

Please add comments / etc if you file additional tickets related to map and I'll add them to the description

Issues

• Filter crashes when the input schema contains a map #8262
• Create a scalar from array of type Map #6485
• Support Map as a ScalarValue #11128
• Implement a scalar function for creating ScalarValue::Map  #11268
• Implement the rewrite from the Map literal to Map function #11434
• Document the Map function in the documentation #11435
• Support Arrays for the Map scalar functions #11436
• Enforce the uniqueness of map key name for the map/make_map function #11437
• Easier Dataframe API for map #11546
• Support Map literal syntax for DuckDB and Generic datafusion-sqlparser-rs#1344
• Support map_keys function for Map type #12147
• Support map_values for MAP type #12148

[goldmedal]

I have created the follow-up issues for #11268:

• Implement the rewrite from the Map literal to Map function #11434
• Document the Map function in the documentation #11435
• Support Arrays for the Map scalar functions #11436
• Enforce the uniqueness of map key name for the map/make_map function #11437

[alamb]

I have created the follow-up issues for #11268:

Awesome -- thank you @goldmedal -- I added them to the ticket description too (as I think this then generates back links on the issues themselves to the epic)

[goldmedal]

I guess it's also related to this epic

• Easier Dataframe API for map #11546

[Weijun-H]

related

• Support map_keys function for Map type #12147
• Support map_values for MAP type #12148

[alamb]

It looks to me like we have completed most of the planned work here and it is no longer active so closing it down to clean up our tickets a bit. Thanks again everyone