New term optimisation #26
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RashmiRam
approved these changes
Aug 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
-> Removed Refresh Interval - as it could interfere with the threshold feature
-> Threshold : Whenever a new term occurs, a event window is created for the same and when the count for the window reaches threshold, an alert is triggered. Once an alert is triggered for a term, it is considered as an existing or old term.
-> Threshold_duration: window duration to store the count of new terms for, when ever new count is appended to the window, the counts added before this duration is decremented.
Threshold_duration names :
-> threshold_window_size
-> threshold_buffer_time
-> buffer_time
-> threshold_waiting_time