You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The above basic example presents an ECS mapped event using field set array reuse. The previous object is process.* field set reused at process.previous.
The normalize: [ 'array' ] setting controls when a particular field expects an array of values. There's no dedicated array type in Elasticsearch, and any field can contain zero or more values of the same type. So when the array attribute is specified, a note is added by the generator script to that field's description in the ECS docs.
Field def setting:
- name: examplenormalize:
- array
Results in this text added to field's description:
Proposed design
Implement a similar mechanism as leaf fields:
specify an attribute on a field reuse
have the asciidoc generator handle including that content in the field reuse description
Open question(s)
Do we reuse the existing normalize attribute convention? Or a simple bool parameter (e.g., is_array)?
The text was updated successfully, but these errors were encountered:
Purpose
Indicate in the field definitions when a field set reuse expects an array.
Background
Reuses allowing arrays may benefit specific limited use. However, there's currently no way to declare this reuse type in the ECS tooling.
The above basic example presents an ECS mapped event using field set array reuse. The
previous
object isprocess.*
field set reused atprocess.previous
.The
normalize: [ 'array' ]
setting controls when a particular field expects an array of values. There's no dedicatedarray
type in Elasticsearch, and any field can contain zero or more values of the same type. So when thearray
attribute is specified, a note is added by the generator script to that field's description in the ECS docs.Field def setting:
Results in this text added to field's description:
Proposed design
Implement a similar mechanism as leaf fields:
Open question(s)
normalize
attribute convention? Or a simplebool
parameter (e.g.,is_array
)?The text was updated successfully, but these errors were encountered: