[bugfix] Init BrokerQueryEventListener #13995
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During testing of release-1.2, we discovered that our broker query event listener framework was not functioning as expected. When initializing the BrokerQueryEventListener, we call the
init
method with configurations needed for pushing messages to Kafka and M3. However, after the release, we stopped receiving messages in both systems.It appears that during the refactoring in #13179, we missed the call to
_brokerQueryEventListener.init(config);
after creating the listener instance. This PR reintroduces that missing call.