Graylog2/graylog2-server

Pipeline stream connections are not deleted when deleting a pipeline

Open

#21,008 建立於 2024年11月20日

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

描述

When deleting a pipeline, all dependent data should also be deleted. In particular for collection pipeline_processor_pipelines_streams:

  • delete the pipeline ID from all pipeline_ids lists
  • delete the entire document, if the deleted pipeline ID was the only one in that connection

Caveat: never delete the default stream connection of the default routing pipeline "All Messages Routing". See Graylog2/graylog-plugin-enterprise/issues/9589 for context.

Current Behavior

Obsolete connection documents remain in the DB.

Steps to Reproduce (for bugs)

  1. Create a pipeline and connect it to a stream
  2. Delete the pipeline
  3. Observe that the pipeline ID is still part of a connection document

Your Environment

  • Graylog Version: 6.2

貢獻者指南

技術棧
javamongodb
領域
backenddatabase
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
JavaMongoDBGraylog pipeline concepts
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
65
研究方向
Investigate the pipeline deletion logic in the Graylog backend. Look for the service that handles pipeline deletion and ensure that after removing a pipeline, the associated stream connections in collection 'pipeline processor pipelines streams' are also cleaned up. Check the caveat for the default stream connection of 'All Messages Routing' as referenced in the enterprise plugin issue. Examine the existing tests to understand expected behavior and add unit tests for this scenario.
Pipeline stream connections are not deleted when deleting a pipeline · Graylog2/graylog2-server#21008 | Good First Issue