elastic/kibana

Kibana Snapshot and Restore UI does not list non-searchable snapshot backing indices for a data stream restore

Open

#179,221 创建于 2024年3月22日

在 GitHub 查看
 (7 评论) (0 反应) (1 负责人)TypeScript (19,065 star) (8,021 fork)batch import
Feature:Snapshot and RestoreTeam:Kibana Managementbuggood first issuetriage_needed

描述

Kibana version: 7.17.8 Elastic Cloud

Elasticsearch version: 7.17.8 Elastic Cloud

Describe the bug: When attempting to restore a backing index from a data stream using the Kibana -> Stack Management -> Snapshot and Restore UI. The UI does not find the backing index even though it is listed in the snapshot.

Steps to reproduce:

  1. Create data stream that is saved to snapshots but not part of any searchable snapshots.
  2. Verify that backing indices exist in a snapshot
  3. Try to restore the same backing index using the Kibana UI which will give you the error below:

There is a workaround for this by using the Restore API.

Expected behavior: The UI should allow you to restore an index like this the same way the Restore API does. The code is filtering out any backing indices, if that can be removed it should fix this.

贡献者指南

技术栈
typescriptreact
领域
datafrontend
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
2
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
TypeScriptReactKibana plugin structure
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
85
研究方向
Examine the file step logistics.tsx at line 67 in the snapshot restore plugin. The filter that excludes backing indices from the list needs to be removed or modified to allow non searchable snapshot backing indices to appear for data stream restore. Ensure that the change does not inadvertently include searchable snapshot indices or other unwanted entries. Review existing tests for the restore snapshot form to cover this case.