4paradigm / 4paradigm/OpenMLDB

Support rows_range Window to slide with determined order

Offen
#1,144 0 Kommentare 0 Reaktionen 3 zugewiesene Personen Beansprucht von @jingchen2222 Auf GitHub ansehen
enhancement
Vorherrschende Sprache
C++
Sterne
1.7k
Forks
331
Ø Merge
12 T. 12 Std.
Gemergte PRs (30 T.)
1

Beschreibung

**Is your feature request related to a problem? Please describe.**

OpenMLDB supports `ROWS_RANGE` syntax to define a window sliding by rows. However, when the dataset contains multiple rows sharing the same order value, the corresponding window rows will be variant since the random order of these rows.

In this issue, we are going to perform a window slide in a determined order so that the window and window aggregation results will be identical no matter how many times we perform window computation.

**Describe the solution you'd like**

- Assigned a determined row_id to the data rows
- Window slide based on the order column and the row_id automatically.
- ordered id should be associated with the online data coming order.

**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.

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

The issue is about the ROWS_RANGE window function in OpenMLDB. Look at the SQL parser and window execution logic, likely in src/parser or src/engine. Understand how rows are ordered and assigned row_ids. The goal is to make window results deterministic when rows share the same order value. Check existing tests for window functions to see the expected behavior.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
sql
Bereich
databases, machine-learning
Issue-Typ
Feature
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.