goldmedal opened a new issue, #13478: URL: https://github.com/apache/datafusion/issues/13478
### Is your feature request related to a problem or challenge? It's similar to https://github.com/apache/datafusion/issues/13477. We use the scalar function to handle the Map type but we should unparse it back to the right SQL. ## Map Literal The SQL for creating a MAP: ``` sql select MAP {'a': 1, 'b': 2} ``` The plan: ``` Plan: Projection: map(make_array(Utf8("a"), Utf8("b")), make_array(Int64(1), Int64(2))) EmptyRelation ``` Unparse the plan: ```sql SELECT map(make_array('a', 'b'), make_array(1, 2)) ``` ## Access a MAP The SQL for accessing a MAP: ```sql select map_col['a'] from (select MAP {'a': 1, 'b': 2} as map_col) ``` The plan: ``` Projection: get_field(map_col, Utf8("a")) Projection: map(make_array(Utf8("a"), Utf8("b")), make_array(Int64(1), Int64(2))) AS map_col EmptyRelation ``` Unparse the plan ```sql SELECT get_field(map_col, 'a') FROM (SELECT map(make_array('a', 'b'), make_array(1, 2)) AS map_col) ``` ### Describe the solution you'd like The SQL should be able to roundtrip for SQL-Plan-SQL. - The `map` with `make_array` function should be unparsed to `ast::Expr::Map` - The `get_fields` for MAP should be unparsed to `ast::Expr::MapAccess` ### Describe alternatives you've considered _No response_ ### Additional context _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
