adds optional window function to aggregate functions in sqlparser

[CoreyWinkelmannPP]

(#5852)

Description

I had a PR for this work before. I went ahead and pushed the changes at the tip of main. Unsure what else I need to do but I am hoping this could be added to the sqlparser so I can move back to using released code again. Thanks!

This adds additional functionality to the sqlparser to support window functions associated to aggregate functions. #4099 new window function capabilities was added but it seemed to miss adding it to aggregate functions like COUNT, SUM, AVG, etc. This will add the OVER CLAUSE associated to existing aggregate functions.

ADDED AGGREGATE FUNCTIONS

AVG()
BIT_AND()
BIT_OR()
BIT_XOR()
COUNT()
MAX()
MIN()
STDDEV_POP(), STDDEV(), STD()
STDDEV_SAMP()
SUM()
VAR_POP(), VARIANCE()
VAR_SAMP()

This does not implement JSON_ARRAYAGG() or JSON_OBJECTAGG() and the related over clause that can be added to them.

Related Issue(s)

#4099
#5852

Checklist

• "Backport to:" labels have been added if this change should be back-ported to release branches
• If this change is to be back-ported to previous releases, a justification is included in the PR description
• Tests were added or are not required
• Did the new or modified tests pass consistently locally and on CI?
• Documentation was added or is not required

Deployment Notes

[vitess-bot]

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

• Ensure that the Pull Request has a descriptive title.
• Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

• Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

• Apply the release notes (needs details) label if users need to know about this change.
• New features should be documented.
• There should be some code comments as to why things are implemented the way they are.
• There should be a comment at the top of each new or modified test to explain what the test does.

New flags

• Is this flag really necessary?
• Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

• Each item in Jobs should be named in order to mark it as required.
• If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

• Protobuf changes should be wire-compatible.
• Changes to _vt tables and RPCs need to be backward compatible.
• RPC changes should be compatible with vitess-operator
• If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
• vtctl command output order should be stable and awk-able.

[deepthi]

Thank you for the contribution! @vitessio/query-serving can we give some attention to this PR please?

[GuptaManan100]

We already merged #13444 which has the same changes proposed here.