quarkusio/quarkus

Allow default exporter with additional Quarkiverse exporters

Open

#36,500 建立於 2023年10月16日

在 GitHub 查看
 (6 留言) (0 反應) (0 負責人)Java (12,967 star) (2,464 fork)batch import
area/tracinggood first issuekind/enhancement

描述

Description

Currently, when an exporter is present the default exporter in not instantiated. A list of exporters through CDI is possible with Quarkiverse exporters because users can activate and deactivate each one individually, however, we need a new property to activate the default exporter, even if other ones are present. This way we can have many different exporters and the default, working together with CDI.

貢獻者指南

技術棧
java
領域
backend
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
JavaCDIQuarkus extension system
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
Examine the current exporter instantiation logic in Quarkus core, likely within the 'quarkus core' module. Look for how the default exporter is created and conditionally disabled when other exporters are present. The issue suggests adding a new configuration property (e.g., 'quarkus.exporter.default.enabled') to force enable the default exporter. Investigate the Quarkus configuration layer and CDI bean registration to implement the toggle. Check if any similar patterns exist in Quarkiverse exporter extensions.