4paradigm / 4paradigm/OpenMLDB
Engine optimize: optimize time expression based on time column index
- 主要言語
- C++
- スター
- 1.7k
- フォーク
- 331
- 平均マージ
- 12日 12時間
- マージ済み PR(30日)
- 1
説明
**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.
コントリビューションガイド
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- sql
- 領域
- database, performance
- issue の種類
- 機能追加
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 活発さ
- 停滞
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 30/100