Nik Everett
Nik Everett
Well this slipped through the cracks. Looks sensible though.
elasticmachine test this please
testing robot, wakeup
Here are some examples of the kind of things you can tell from these numbers:   The second example shows that our `CASE` function is really slow - we...
Floating this to the top level - we might wish to rework the Status objects into `Map` and let the serialization just flow. The way I've designed this is quite...
I think there are cases where I really *do* want to dig into these, at least the ObjectStatus subclasses. Not now, but we've talked about making a progress bar like...
Ok. I've decided I don't want to make a generic status response. No `Map` or `String[], long[]` or whatever. It might be ok, but there's momentum with this and I'm...
Oh yeah build passed!
> * Double-check exception management (ie. make sure that all the exceptions thrown are `EsqlClientException`, and not only `QlClientException`) The rest of Elasticsearch doesn't really use special exceptions for a...
> @mosche this exception is thrown because the feature service is assuming that if you are checking for a feature, the feature should be registered _somewhere_, yes? This fallback thing...