Skip to content

Commit 98e3228

Browse files
docs: clarify that managed data views cannot be deleted (#7436)
1 parent 763813f commit 98e3228

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

explore-analyze/find-and-organize/data-views.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,8 @@ In certain apps, you can also query your {{es}} data using [{{esql}}](elasticsea
2828
* If a read-only indicator appears, you have insufficient privileges to create or save {{data-sources}}. In addition, the buttons to create {{data-sources}} or save existing {{data-sources}} are not visible.
2929
* {applies_to}`stack: ga 9.2` Some data views are exclusively configured and **managed** by Elastic. You can view and use these managed data views, but you can't edit them. If you'd like to use a modified version of a managed data view, you can [duplicate it](#duplicate-managed-data-view) and edit that new copy as needed.
3030

31+
{applies_to}`stack: ga 9.4` You also can't delete a managed data view.
32+
3133

3234
## Create a data view [settings-create-pattern]
3335

@@ -170,6 +172,8 @@ To restrict a {{data-source}} to specific projects regardless of the active scop
170172

171173
When you delete a {{data-source}}, you cannot recover the associated field formatters, runtime fields, source filters, and field popularity data. Deleting a {{data-source}} does not remove any indices or data documents from {{es}}.
172174

175+
{applies_to}`stack: ga 9.4` You can't delete managed data views. On the **Data Views** management page, the delete action isn't available for these data views, and they can't be selected for bulk deletion. To use a modified version of a managed data view, [duplicate it](#duplicate-managed-data-view) instead.
176+
173177
::::{warning}
174178
Deleting a {{data-source}} breaks all visualizations, saved Discover sessions, and other saved objects that reference the data view.
175179
::::

0 commit comments

Comments
 (0)