4paradigm / 4paradigm/OpenMLDB
Engine optimize: optimize time expression based on time column index
- Lingua principale
- C++
- Stelle
- 1.7k
- Fork
- 331
- Merge medio
- 12g 12h
- PR unite (30g)
- 1
Descrizione
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
### Example:
```SQL
SELECT t1.*, t2.* from t1
LAST JOIN t2 ORDER BY t2.std_ts
ON t1.id=t2.id and t2.std_ts BETWEEN timestamp("2021-01-01") and timestamp("2021-06-01");
```
We would like to optimize join with BETWEEN ... AND expression
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
The issue mentions optimizing a JOIN with a BETWEEN expression on a time column. Look for the engine's query optimizer code, likely in a directory like src/optimizer or src/engine. Search for existing time-based optimizations or index usage. The goal is to modify the optimizer to recognize and leverage a time column index for range predicates in JOIN conditions. Testing would involve SQL queries with BETWEEN on timestamp columns to verify performance improvement.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- sql
- Ambito
- database, performance
- Tipo di issue
- Funzionalità
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 30/100