elastic/elasticsearch

Detect when copying to a non-existent field when dynamic mappings are disabled

Open

#112,812 建立於 2024年9月12日

在 GitHub 查看
 (20 留言) (0 反應) (0 負責人)Java (76,700 star) (25,882 fork)batch import
:Search Foundations/Mapping:Search Relevance/Search>enhancementTeam:Search FoundationsTeam:Search Relevancegood first issue

描述

Description

We should be able to detect when a user is attempting to use copy_to to copy to a non-existent field when dynamic mappings are disabled. For example:

PUT test-index
{
  "mappings": {
    "dynamic": false,
    "properties": {
      "test_field": {
        "type": "text",
        "copy_to": "missing_field"
      }
    }
  }
}

Currently, this request succeeds even though nothing will ever be copied to missing_field. We should throw a 400 error in this case to indicate to the user that their mappings are invalid.

貢獻者指南

技術棧
javarest api
領域
backendapi
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
JavaElasticsearch mapping conceptsUnderstanding of dynamic mapping
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
45
研究方向
Investigate the mapping parsing code where copy to is handled, likely in classes like MappingMetaData or FieldMapper. Examine the logic that validates field existence when dynamic is false. Consider how to integrate a check that throws an exception. Review the existing test suite for mapping validation to understand patterns. Check the issue comments for any suggested approaches.
Detect when copying to a non-existent field when dynamic mappings are disabled · elastic/elasticsearch#112812 | Good First Issue