You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2022/03/24 11:46:08 UTC

[GitHub] [dolphinscheduler] github-actions[bot] commented on issue #9174: [Feature][Alarm] About alarm information deduplication

github-actions[bot] commented on issue #9174:
URL: https://github.com/apache/dolphinscheduler/issues/9174#issuecomment-1077540147


   ### Search before asking
   
   - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
   
   
   ### Description
   
   <img width="974" alt="截屏2022-03-24 下午7 30 58" src="https://user-images.githubusercontent.com/1137341/159907826-1ece398b-a4f9-4ef0-83a6-c96af32e5b2f.png">
   The current implementation uses the above sql in order to avoid duplication of alarm information.
   
   its disadvantages:low performance.
   
   Right way:When an alarm is generated, an alarm ID is generated
   
   Recommended open source library:
   [timeflake4j](https://github.com/making/timeflake4j)
   
   ### Use case
   
   Improve performance
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org