Nicolas Ruflin

It looks like this change comes from https://github.com/ruflin/Elastica/pull/1765 I think the goal was to cleanup the code but it looks like it had an unexpected side effect. @thePanz As you...

What speaks for 2, is that there is just one way of doing things which should simplify code maintenance. What speaks for 1 is that it removes the breaking change...

I'm ok with the proposal from @pandafox to keep it backward compatible in 7.x and make the "breaking change" in 8.x with the exception like this our 8.x code is...

I would actually consider this a feature even though I didn't know it would be possible to first go to ES|QL and then back to Discover and still have it....

As your use case is not the typical logging use case where the mod date would be constantly changing, I could also think of a solution which involves creating a...

It doesn't directly, but it can solve it. The problem today is that an `add_field` processor is used to set this field. Having it configured as a config option by...

We had similar discussions recently in the context otel / semconv mappings. The way I think of these alias is like a hardlink, all are the originals but reference the...

My ideal scenario would be that Elasticsearch versions its assets like ingest pipeline, index templates which would not only allow to track changes (also historically) but allow to roll back...

> We do have these for some of our configuration items (like ILM policies), and we can expand that list fairly easily. There's a little bit of a discussion around...

Can you share some more details why you picked the example you have above over: ``` { "_ignore_malformed": ["foo", "bar"] "_ignore_above": ["goo", "gar"] } ``` As I would assume the...