-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Window function fails to demarcate if 2 following are used #15739
Comments
some testcases which should start working if this is fixed:
|
10 tasks
abhishekagarwal87
pushed a commit
that referenced
this issue
Feb 2, 2024
introduce checks to ensure that window frame is supported added check to ensure that no expressions are set as bounds added logic to detect following/following like cases - described in Window function fails to demarcate if 2 following are used #15739 currently RANGE frames are only supported correctly if both endpoints are unbounded or current row Offset based window range support #15767 added windowingStrictValidation context key to provide a way to override the check
kgyrtkirk
added a commit
to kgyrtkirk/druid
that referenced
this issue
Feb 2, 2024
introduce checks to ensure that window frame is supported added check to ensure that no expressions are set as bounds added logic to detect following/following like cases - described in Window function fails to demarcate if 2 following are used apache#15739 currently RANGE frames are only supported correctly if both endpoints are unbounded or current row Offset based window range support apache#15767 added windowingStrictValidation context key to provide a way to override the check (cherry picked from commit 8f5b752)
kgyrtkirk
added a commit
to kgyrtkirk/druid
that referenced
this issue
Feb 2, 2024
introduce checks to ensure that window frame is supported added check to ensure that no expressions are set as bounds added logic to detect following/following like cases - described in Window function fails to demarcate if 2 following are used apache#15739 currently RANGE frames are only supported correctly if both endpoints are unbounded or current row Offset based window range support apache#15767 added windowingStrictValidation context key to provide a way to override the check (cherry picked from commit 8f5b752)
abhishekagarwal87
pushed a commit
that referenced
this issue
Feb 5, 2024
introduce checks to ensure that window frame is supported added check to ensure that no expressions are set as bounds added logic to detect following/following like cases - described in Window function fails to demarcate if 2 following are used #15739 currently RANGE frames are only supported correctly if both endpoints are unbounded or current row Offset based window range support #15767 added windowingStrictValidation context key to provide a way to override the check (cherry picked from commit 8f5b752)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At this moment on Druid master, a query like
AND
are planned identically with the native query showing the same offset in the processor for both
Going forward we need to demarcate these cases and make sure we support negative offsets in such a case. At the moment even in native you cannot specify
which throws an IndexOutOfBounds exception.
Steps to reproduce
The csv used in the above query is:
us_ecom_orders_com101.csv
Another easy way to reproduce using the druid foo table is
The text was updated successfully, but these errors were encountered: