Skip to content

Tracking: improve aggreagation fuzzer #15870

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

Open
Rachelint opened this issue Apr 27, 2025 · 0 comments
Open

Tracking: improve aggreagation fuzzer #15870

Rachelint opened this issue Apr 27, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@Rachelint
Copy link
Contributor

Rachelint commented Apr 27, 2025

Is your feature request related to a problem or challenge?

I found aggregation fuzzer are still hard to use when I act as an user currently.
Some points I noticed can be improved:

1. Aggregation function generation

Now it is still hard/possible to generate sql having multiple aggregated functions like:

SELECT count(string), sum(number) FROM xxx GROUP BY xxx;

It is due to aggregate_function and aggregate_arguments are set respectively. if we set mutiple aggregate_functions, columns in the respectly set aggregate_arguments may be not supported in some of the aggregate_functions.
For example,

If we set:
aggregate_arguments: [string, primitive]
aggregate_function: [sum, count]

Then wrong generated sql possible to be generated:
SELECT sum(string) FROM t GROUP BY xxx

2. Group by columns ordering

Noticed by @jayzhan211 , it is hard to control the ordering of group by columns right now.
#15851 (comment)

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response

@Rachelint Rachelint added the enhancement New feature or request label Apr 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant