One more detail: we should not throw exceptions from Parser (need to just return false instead).
Because Query Fuzzer is incompatible with it. Example:
https://clickhouse-test-reports.s3.yandex.net/16366/6ec602ad67843a3e2554aed4b1f3fefd10d6ec52/fuzzer/fuzzer.log

One more detail: we should not throw exceptions from Parser (need to just return false instead).
Because Query Fuzzer is incompatible with it. Example:
https://clickhouse-test-reports.s3.yandex.net/16366/6ec602ad67843a3e2554aed4b1f3fefd10d6ec52/fuzzer/fuzzer.log

There are many throw Exception in parser, should we remove all of them?

There are many throw Exception in parser, should we remove all of them?

Not necessarily, there are some useful cases... I will fix Fuzzer in another way.

Now we have to fix the remaining cases:

f(ALL)
f(ALL, x)

ALL should be treat as identifier.

f(ALL x)

Here ALL should be treat as noop.

Maybe also do the same fixes for DISTINCT:

SELECT f(DISTINCT)
SELECT f(DISTINCT, x)

Now we have to fix the remaining cases:

f(ALL)
f(ALL, x)

ALL should be treat as identifier.

f(ALL x)

Here ALL should be treat as noop.

But if the query is SELECT f(ALL) FROM table, what does it mean?

It means that the table presumable has a column named ALL.
Example:

SELECT exp(ALL) FROM (SELECT 1 AS ALL)

#19029

I cannot understand why "Docs check" has failed. Just removed the link.