Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(flink): fix compilation of over aggregation query in flink backend #8359

Merged
merged 4 commits into from
Feb 23, 2024

Conversation

chloeh13q
Copy link
Contributor

@chloeh13q chloeh13q commented Feb 14, 2024

Description of changes

This PR fixes the compilation of over aggregation query in Flink backend.

I identified the following issues:

  1. The interval time value is not compiled with the appropriate precision. ibis.interval(minutes=500) compiles to `INTERVAL '500' MINUTE, which throws
org.apache.calcite.sql.validate.SqlValidatorException: Interval field value 500 exceeds precision of MINUTE(2) field
  1. range=(-ibis.interval(minutes=500), 0) compiles to [...] AND CAST(0 AS INTERVAL MINUTE) following and Flink doesn't support rows/range following in over aggregation. This throws
org.apache.flink.table.api.TableException: OVER RANGE FOLLOWING windows are not supported yet.

I also removed the unused test snapshot directory that didn't get cleaned up.

Issues closed

@chloeh13q chloeh13q force-pushed the fix/flink-over-window branch 3 times, most recently from 84c5e3e to 438846d Compare February 14, 2024 21:40
@chloeh13q chloeh13q marked this pull request as ready for review February 23, 2024 13:07
@cpcloud cpcloud added this to the 9.0 milestone Feb 23, 2024
@cpcloud cpcloud added bug Incorrect behavior inside of ibis flink Issues or PRs related to Flink labels Feb 23, 2024
@cpcloud cpcloud merged commit de174a2 into ibis-project:main Feb 23, 2024
74 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Incorrect behavior inside of ibis flink Issues or PRs related to Flink
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants