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?
This is a follow on to the discussion in #15646 where the user would like to have metadata specified on literal values.
Describe the solution you'd like
I do not have a specific plan in mind, but I could imaging that the literal functions that take in a scalar value could take in some optional metadata and store it. Then when the return_field_from_args gets called, the metadata would be available. I think we also should solicit some additional use case from the originator of the idea.
Describe alternatives you've considered
There is a work around where the user can write their own simple scalar UDF to handle this.
Additional context
No response
The text was updated successfully, but these errors were encountered:
I believe I've tracked the issue down to create_physical_expr in the planner. This is where we are losing metadata. I think this is a relatively easy fix.
In addition to the above, we are dropping metadata during optimizer, specifically it looks like it is happening at the OptimizeProjections rule. Still investigating.
Is your feature request related to a problem or challenge?
This is a follow on to the discussion in #15646 where the user would like to have metadata specified on literal values.
Describe the solution you'd like
I do not have a specific plan in mind, but I could imaging that the literal functions that take in a scalar value could take in some optional metadata and store it. Then when the
return_field_from_args
gets called, the metadata would be available. I think we also should solicit some additional use case from the originator of the idea.Describe alternatives you've considered
There is a work around where the user can write their own simple scalar UDF to handle this.
Additional context
No response
The text was updated successfully, but these errors were encountered: