UnamedRus

It's actually common to query builders to write conditions like ``` WHERE has(friends, 'Alice') = 1; WHERE has(friends, 'Alice') = true; ``` Because, not everywhere 1 is expected argument for...

``` SELECT * FROM system.completions WHERE prompt = 'xxxxx|' ``` Will return list of possible completions from `Suggest.h` with weights?

> is tied to altering files' properties (last changed time and to) and it's impossible to remove this BTW, there are plans to remove dependency on (at least) `changed_time` property...

Do we actually need to have separate procedure for all combinations, normal s3/zero copy s3 and etc? Ie, if someone want to migrate just ask him to add new vfs...

IMO, it should be separate keyword, because `LIMIT 1` is vague. (but still meaningful) LIMIT QUANTILE

> or 2-digit fractions [0.99, 0.75, etc.], are also required Could it be arbitrary fraction?, ie AFAIK parser should just support like float64 for parsing of decimals. > so is...

Actually, may be you can just reuse code from SAMPLE feature? https://clickhouse.com/docs/sql-reference/statements/select/sample#sample-k It have quite a few common points? It is normal limit or you introduced some other keyword? https://fiddle.clickhouse.com/f7d34f51-2753-489a-a9d8-07c95b1bc1c2...

> It's a normal limit with fractions representing percentages, like mentioned in the issue description. My concern with this approach, that LIMIT 1 have meaning as get 1 row (which...

> And we may assume that if one wants the entire dataset, i guess he won't be using LIMIT? Well, if it written by hand, then sometimes :) There are...

Few more ``` groupH3Intersect groupH3Union ``` Takes arbitrary H3 indexes, and return minimal combination of h3 indexes, which fill covered area by them. You can also pass refunction to merge...