Nik Everett

> Isn't this what the BwC tests are for? It's not great relying on ordering in code, but we would know pretty quickly if we did change something incompatibly, as...

I think Ryan's right about how this should move in the end, but I still think we should deprecate these. I'd prefer to have wordy hand written serialization than sneaky...

We're planning to implement this by splitting the query into two commands internally, then running them in a row. So, this: ``` FROM foo | INLINESTATS MIN(b) BY a |...

The main limitation of this approach is that the results of the first `STATS` result has to be small enough you can push it across the wire. That's going to...

> I think for this specific case it makes sense to consider `null` values as empty arrays, so that That's fine - our `null` is basically an empty list. I'd...

> It is pretty uncommon for ESQL (all the other functions, apart from `COALESCE`, short-circuit to `null` when one of the values is null), so let's discuss this behavior. There's...

I think this one is similar to this: ``` REPRODUCE WITH: ./gradlew ':docs:yamlRestTest' --tests "org.elasticsearch.smoketest.DocsClientYamlTestSuiteIT.test {yaml=reference/esql/esql-rest/line_297}" -Dtests.seed=53ABCE485C630DC4 -Dtests.locale=hu -Dtests.timezone=Asia/Irkutsk -Druntime.java=21 ```

We already automate the parameter types and the railroad diagrams. But we could probably generate even more of this stuff. I'm not sure we'd want to generate all of, but...

Right now we generate two files and manually make another "main" file with the description and the name and description and an example. But I'll bet we could generate that...

I've automated the generation of the signature, examples, and parameters. And a file that links them all together. Basically all of this. A human being has to manually merge the...