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.