Graylog2/graylog2-server

Empty indices are incorrectly included in the search target

Open

#6,016 建立於 2019年6月16日

在 GitHub 查看
 (5 留言) (0 反應) (0 負責人)Java (6,945 star) (1,032 fork)batch import
bugelasticsearchgood first issuetriaged

描述

Empty indices are INCORRECTLY included in the search target

Expected Behavior

Only indices with messages should be targeted

Current Behavior

Empty indices are INCORRECTLY targeted in EVERY search

Steps to Reproduce (for bugs)

  1. Make sure that you have at least one empty index which is NOT active write index
  2. Make a search using what ever settings you like
  3. Empty index is included in the search target

Screen Shot 2019-06-16 at 19 31 20

Screen Shot 2019-06-16 at 19 32 21

Screen Shot 2019-06-16 at 19 32 06

Context

Confuses user when it seems that a simple queries might seem to target multiple indices

Your Environment

  • Graylog Version: 3.0.1
  • Elasticsearch Version: 6.7.2
  • MongoDB Version: 4.0.7
  • Operating System: CentOS 7
  • Browser version: Safari

貢獻者指南

技術棧
javaelasticsearchmongodb
領域
backenddatabasesearch
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Java programmingElasticsearch basics
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
Investigate the search query construction in the Graylog codebase, specifically the logic that determines which indices to include. Look for a filter that should exclude empty indices but is missing or incorrect. Check if there are any related test cases or existing discussions in the issue comments for additional context. Start by examining the `SearchService` or index routing classes in the Java source.
Empty indices are incorrectly included in the search target · Graylog2/graylog2-server#6016 | Good First Issue