Skip to content

Pore over all existing text fields to identify more that should be multi-fields #104

@webmat

Description

@webmat

Moving from keyword only indexing to multi-fields is a breaking change, so we need to make sure we're consistent with this.

  • Review all current textual fields with an open mind and consider if they could benefit from being multi-field.
    • Since we currently do keyword by default, the question will mostly be: would we benefit from the ability to do partial searches on these values? E.g. filter for "guest" or "wifi" in field network.name or "prod" in host.name.
  • Document this as an ECS convention: we consider doing multi-fields on any non-trivial text field.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions