You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem or challenge?
Based on the discussion in #11268 (comment), we will support the MAP literal to create a map value. Referring to the DuckDB syntax, we can use syntax like:
SELECT MAP {'key1': 10, 'key2': 20, 'key3': 30};
Describe the solution you'd like
After #11361, we now have two functions: map and make_map. We can use UserDefinedSQLPlanner to implement the proposed syntax and rewrite it to the map function. As @jayzhan211 mentioned in #11361 (comment), we can also use ExprPlanner to handle the make_map function. Since make_map is less efficient than the map function, we should retain only the faster map scalar function implementation. For more details, see the previous discussions and benchmark results in #11361.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
I found the MAP literal isn't supported by the sqlparser-rs. I think we need to implement this syntax on the sqlparser-rs side first. However, I think I can have a PR for moving make_map to ExprPlanner first.
What do you think? @jayzhan211
Is your feature request related to a problem or challenge?
Based on the discussion in #11268 (comment), we will support the MAP literal to create a map value. Referring to the DuckDB syntax, we can use syntax like:
Describe the solution you'd like
After #11361, we now have two functions:
map
andmake_map
. We can useUserDefinedSQLPlanner
to implement the proposed syntax and rewrite it to themap
function. As @jayzhan211 mentioned in #11361 (comment), we can also useExprPlanner
to handle themake_map
function. Sincemake_map
is less efficient than themap
function, we should retain only the fastermap
scalar function implementation. For more details, see the previous discussions and benchmark results in #11361.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: