Open tobackes opened 8 months ago
Are you sure you cannot use some existing SQL engine somehow?
Our SQL interface translates directly to Polars calls, so clearly we cannot use a different one. If you want/need to use a different engine you can just go and use that engine - but we can't as we're translating a SQL query to Polars-native code ;)
I saw there were already previous bugs in interpreting window function queries.
Do you have some links to the related Issues? Could be helpful to link them together. If not, do feel free to submit them as new Issues or attach them to this one 👍
Checks
Reproducible example
Log output
Issue description
There seems to be a bug in the execution of window functions in polars SQLContext.
This is a combination of PARTITION BY and ORDER BY.
(Totally inappropriate and unqualified question: Are you sure you cannot use some existing SQL engine somehow? I saw there were already previous bugs in interpreting window function queries.)
Expected behavior
The expected behavior is shown in the second table in the output. The problematic behavior is shown in the first table.
In the minimal example, the sum should be over the previous row values until the new group stars and then begin from 1.
That means it should be [1,2,3,1,2,3]
Installed versions