Show _ignored field in Discover

[flash1293]

Summary

Closes #184669

To test:

PUT my-ignored-index
{
  "mappings": {
    "properties": {
      "a": {
        "type": "keyword",
        "ignore_above": 10
      }
    }
  }
}

POST my-ignored-index/_doc
{
  "a": "abc"
}

POST my-ignored-index/_doc
{
  "a": "abcabcabcabcabcabcabcabc"
}

[apmmachine]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

[jughosta]

Works great, thanks!

[flash1293]

/ci

[peteharverson]

In ML we omit metadata fields in a number of places in our UI. Would you be able to add _ignored into this list:

kibana/x-pack/packages/ml/anomaly_utils/field_types.ts

Line 47 in a03f3bc

export const OMIT_FIELDS: string[] = [

@qn895 we also have that same OMIT_FIELDS list for the data visualizer:

https://github.com/elastic/kibana/blob/main/x-pack/plugins/data_visualizer/common/constants.ts#L54

For consistency, I'm thinking we should add _ignored to that list too, but I can't recall why we don't want to show some of those metadata fields. For example, _ignored seems to be handled OK:

[flash1293]

Thanks @peteharverson - added to the omit array

[jughosta]

Hopefully addressed the remaining test failures via flash1293#14

[qn895]

ML changes LGTM 🎉

[flash1293]

Wow, thanks a ton, @jughosta - merged it in, let's see whether it works (fingers crossed)

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: b1d0b80

The CI Stats report is too large to be displayed here, check out the CI build annotation for this information.

History

• 💔 Build #215133 failed 2a55957
• 💚 Build #215029 succeeded 069c964
• 💔 Build #214674 failed 2d808c7
• 💔 Build #214627 failed 85bf6c3
• 💔 Build #214505 failed da040d7
• 💔 Build #214434 failed c9b0cc0

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[eokoneyo]

Shared UX changes LGTM