Adding match_only_text subfield to *.display_name fields

[eyalkoren]

Changing ecs@mappings to match the new ECS definitions that were added in elastic/ecs#2547.
*.display_name fields were already mapped as keyword, but this PR adds a match_only_text subfield called text.

[elasticsearchmachine]

Pinging @elastic/es-data-management (Team:Data Management)

[elasticsearchmachine]

Hi @eyalkoren, I've created a changelog YAML for you.

[eyalkoren]

@mjwolf can you tell what these serverless test failures are about?

[felixbarny]

Oh, I think we have to increment the version in the stack template registry.

[dakrone]

Yes, that will need to be incremented.

[mjwolf]

@mjwolf can you tell what these serverless test failures are about?

I'm not sure what serverless test failures you're referring to?

[dakrone]

I'm not sure what serverless test failures you're referring to?

There were some transient compilation failures that were unrelated to this change, in the ML project. They're gone after merging master.

[eyalkoren]

Right, the registry version 🙁
I really wish there was a way to stop relying on this manual versioning.
How about relying on a combined hash of all templates instead to decide whether templates need to be upgraded?

[eyalkoren]

Again serverless build fail with unrelated error, but this time branch update doesn't help 🙁

[felixbarny]

I really wish there was a way to stop relying on this manual versioning.
How about relying on a combined hash of all templates instead to decide whether templates need to be upgraded?

I also always forget to increment the version, and I agree that we should do something about it.

I like your idea. Building on that, I had another one that maybe requires fewer changes. In addition to the version constant, we'd also add a string constant, holding the hash of all templates in a registry. We could make tests fail if the hashes differ which forces you to update the hash, acting as a reminder to increment the version.

Not sure which option I like better. But IIRC, Jimmy's template bulk API idea might change this again so maybe a more incremental improvement makes sense?

[eyalkoren]

In addition to the version constant, we'd also add a string constant, holding the hash of all templates in a registry. We could make tests fail if the hashes differ which forces you to update the hash, acting as a reminder to increment the version.

That's a nice idea! It means that every change would result in a version increment (instead of once per release), but I don't think that's an issue.

[eyalkoren]

Here it is: #136666