-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[8.x] [Fields Metadata] Improve integration fields resolution and cac…
…hing (#195405) (#196086) # Backport This will backport the following commits from `main` to `8.x`: - [[Fields Metadata] Improve integration fields resolution and caching (#195405)](#195405) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Marco Antonio Ghiani","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-10-14T10:15:36Z","message":"[Fields Metadata] Improve integration fields resolution and caching (#195405)\n\n## 📓 Summary\r\n\r\nBrowsing fields from the Discover sidebar, I noticed integration fields\r\nnever show a related description even if they exist. The same is\r\nhappening in the fields table for the document detail flyout.\r\n\r\nThis happens due to `integration` and `dataset` parameters not being\r\npassed to the service.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/0946cc71-44fb-4fc7-8e9d-b146bdd811f2\r\n\r\nThese changes improve the resolution of the integration field metadata:\r\n\r\n- The `integration` and `dataset` params are no longer required to\r\nattempt resolving and integration field metadata.\r\nThey are still accepted as an explicit hint in case we cannot infer\r\ncorrectly some integration packages from the field name.\r\n- The above change enables querying fields from different integrations\r\nand datasets at once, enabling metadata retrieval for mixed data\r\nsources.\r\n- The integration retrieved from the EPR is now cached with its relevant\r\nversion, solving a potential corner case as explained\r\n[here](https://github.com/elastic/kibana/pull/183806#pullrequestreview-2088102130).\r\n\r\n\r\nhttps://github.com/user-attachments/assets/ae9cafd8-2581-4ce0-9242-cbb4e37c7702\r\n\r\n---------\r\n\r\nCo-authored-by: Marco Antonio Ghiani <[email protected]>","sha":"2b7c72c6193cf46c5cf883dafb8521f4a6805cd4","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","backport:prev-minor","Team:obs-ux-logs"],"title":"[Fields Metadata] Improve integration fields resolution and caching","number":195405,"url":"https://github.com/elastic/kibana/pull/195405","mergeCommit":{"message":"[Fields Metadata] Improve integration fields resolution and caching (#195405)\n\n## 📓 Summary\r\n\r\nBrowsing fields from the Discover sidebar, I noticed integration fields\r\nnever show a related description even if they exist. The same is\r\nhappening in the fields table for the document detail flyout.\r\n\r\nThis happens due to `integration` and `dataset` parameters not being\r\npassed to the service.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/0946cc71-44fb-4fc7-8e9d-b146bdd811f2\r\n\r\nThese changes improve the resolution of the integration field metadata:\r\n\r\n- The `integration` and `dataset` params are no longer required to\r\nattempt resolving and integration field metadata.\r\nThey are still accepted as an explicit hint in case we cannot infer\r\ncorrectly some integration packages from the field name.\r\n- The above change enables querying fields from different integrations\r\nand datasets at once, enabling metadata retrieval for mixed data\r\nsources.\r\n- The integration retrieved from the EPR is now cached with its relevant\r\nversion, solving a potential corner case as explained\r\n[here](https://github.com/elastic/kibana/pull/183806#pullrequestreview-2088102130).\r\n\r\n\r\nhttps://github.com/user-attachments/assets/ae9cafd8-2581-4ce0-9242-cbb4e37c7702\r\n\r\n---------\r\n\r\nCo-authored-by: Marco Antonio Ghiani <[email protected]>","sha":"2b7c72c6193cf46c5cf883dafb8521f4a6805cd4"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/195405","number":195405,"mergeCommit":{"message":"[Fields Metadata] Improve integration fields resolution and caching (#195405)\n\n## 📓 Summary\r\n\r\nBrowsing fields from the Discover sidebar, I noticed integration fields\r\nnever show a related description even if they exist. The same is\r\nhappening in the fields table for the document detail flyout.\r\n\r\nThis happens due to `integration` and `dataset` parameters not being\r\npassed to the service.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/0946cc71-44fb-4fc7-8e9d-b146bdd811f2\r\n\r\nThese changes improve the resolution of the integration field metadata:\r\n\r\n- The `integration` and `dataset` params are no longer required to\r\nattempt resolving and integration field metadata.\r\nThey are still accepted as an explicit hint in case we cannot infer\r\ncorrectly some integration packages from the field name.\r\n- The above change enables querying fields from different integrations\r\nand datasets at once, enabling metadata retrieval for mixed data\r\nsources.\r\n- The integration retrieved from the EPR is now cached with its relevant\r\nversion, solving a potential corner case as explained\r\n[here](https://github.com/elastic/kibana/pull/183806#pullrequestreview-2088102130).\r\n\r\n\r\nhttps://github.com/user-attachments/assets/ae9cafd8-2581-4ce0-9242-cbb4e37c7702\r\n\r\n---------\r\n\r\nCo-authored-by: Marco Antonio Ghiani <[email protected]>","sha":"2b7c72c6193cf46c5cf883dafb8521f4a6805cd4"}}]}] BACKPORT--> Co-authored-by: Marco Antonio Ghiani <[email protected]>
- Loading branch information
1 parent
b7c0e07
commit 89623aa
Showing
13 changed files
with
162 additions
and
18 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters