elastic/kibana

[event log] unable to add properties named `meta` to event log doc schema

Open

#158,777 创建于 2023年5月31日

在 GitHub 查看
 (2 评论) (0 反应) (0 负责人)TypeScript (19,065 star) (8,021 fork)batch import
Feature:EventLogTeam:ResponseOpsbuggood first issue

描述

See: https://github.com/elastic/kibana/blob/15b31c62ba8d4a115c359d9bb723147866bbd34c/x-pack/plugins/event_log/scripts/create_schemas.js#L189-L195

It appears the schema generator is looking for meta properties to determine if an ES field is considered an array. And that seems like some dead code, since we specifically call out "array" properties in our schema:

https://github.com/elastic/kibana/blob/15b31c62ba8d4a115c359d9bb723147866bbd34c/x-pack/plugins/event_log/scripts/mappings.js#L278-L285

贡献者指南

技术栈
typescriptnodejs
领域
backenddata
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
under 1 hour
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
familiarity with Kibana event logbasic understanding of Elasticsearch mappings
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
60
研究方向
The issue is about the event log schema generation script at x pack/plugins/event log/scripts/create schemas.js, lines 189-195, which incorrectly checks for a 'meta' property to determine if a field is an array, while the mappings in mappings.js explicitly define array types. The fix should remove or update that dead code. No assignee or PR exists, so the issue is available for contribution.