Time intrinsics support for read_parquet() SQL function
Open
Nobody has claimed this yet.
Enhancement
Performance
- Dominant language
- Java
- Stars
- 17.3k
- Forks
- 1.7k
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 28
Description
Is your feature request related to a problem?
Follow-up for #5293
We need to make designated timestamp intrinsics kick in for pseudo-table functions like read_parquet()
Describe the solution you'd like.
No response
Describe alternatives you've considered.
No response
Full Name:
Andrei Pechkurov
Affiliation:
QuestDB
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the referenced issue #5293 first, then locate the read_parquet() SQL function and the existing designated timestamp intrinsic handling. Determine how pseudo-table functions currently receive time intrinsics, and consider the work complete when the requested intrinsics operate correctly for read_parquet().
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, sql
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100