Another way to get the possible return type of function for information_schema
- Dominant language
- Rust
- Stars
- 9.3k
- Forks
- 2.4k
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 344
Description
### Is your feature request related to a problem or challenge?
As mentioned https://github.com/apache/datafusion/pull/13717#discussion_r1880565471, `return_type` could be deprecated by #13717. We should try to use `return_type_from_exprs` or another method for the information_schema table instead.
The challenge with using `return_type_from_exprs` is that the record generation of `routines` or `parameters` won't have the required expression arguments for it. 🤔
### Describe the solution you'd like
_No response_
### Describe alternatives you've considered
_No response_
### Additional context
_No response_
Contributor guide
Research direction
Start with the discussion in PR #13717 and inspect how the information_schema routines or parameters records currently obtain return types. Determine how to avoid the deprecated return_type API when record generation lacks the expression arguments required by return_type_from_exprs; done means the information_schema tables still produce the required return-type information through an agreed approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, sql
- Domain
- database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100