Graylog2/graylog2-server

Empty indices are incorrectly included in the search target

Open

#6016 opened on Jun 16, 2019

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Java (6,945 stars) (1,032 forks)batch import
bugelasticsearchgood first issuetriaged

Description

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

Contributor guide

Tech stack
javaelasticsearchmongodb
Domain
backenddatabasesearch
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Java programmingElasticsearch basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
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.