-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Allow counters to be created with same name, provider and source as a deleted one #10223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: 4.20
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 4.20 #10223 +/- ##
=========================================
Coverage 15.99% 15.99%
- Complexity 13086 13088 +2
=========================================
Files 5649 5649
Lines 495714 495733 +19
Branches 60017 60018 +1
=========================================
+ Hits 79289 79302 +13
- Misses 407572 407577 +5
- Partials 8853 8854 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
@blueorangutan package |
@Pearl1594 a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 12137 |
@blueorangutan test |
@rohityadavcloud a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one comment,
Also the issue reported that deleteCounter doesn't work. Is that genuine?
engine/schema/src/main/resources/META-INF/db/schema-41910to41920.sql
Outdated
Show resolved
Hide resolved
[SF] Trillian test result (tid-12142)
|
engine/schema/src/main/resources/META-INF/db/schema-41910to41920.sql
Outdated
Show resolved
Hide resolved
This pull request has merge conflicts. Dear author, please fix the conflicts and sync your branch with the base branch. |
engine/schema/src/main/resources/META-INF/db/schema-41910to41920.sql
Outdated
Show resolved
Hide resolved
@blueorangutan package |
@Pearl1594 |
@weizhouapache It allows to create a counter with same name provider and source - as long as the value is different. Is that not expected? |
This pull request has merge conflicts. Dear author, please fix the conflicts and sync your branch with the base branch. |
Thanks for testing @Pearl1594 Can you test with same provider/source/value but different name ? It is the original issue. |
I think the original issue was not being able to create counter with same name, provider and source as a deleted counter However, now that you asked to test it @weizhouapache - I am not sure if this is correct in the first place. |
… non-deleted counter
@weizhouapache I added a fix - could you please verify if the below behaviour is what's expected: Thanks. |
|
@Pearl1594 I checked the
the reporter also mentioned
so it looks like the counter name can be same as other counters, sorry my bad. currently if create a counter with same provider/source/value, it throws exception
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
clgtm
@Pearl1594 what is the status of this? Ar you going to work to apply @weizhouapache 's sugection in #10223 (comment) ? |
I need to revert a change because from an earlier discussion I had made changes to prevent counters from having the same name. But that seems like it should be allowed. So I need to work on this. |
This pull request has merge conflicts. Dear author, please fix the conflicts and sync your branch with the base branch. |
@Pearl1594 can you address the comments and conflict? |
Description
This PR fixes: #10043
Types of changes
Feature/Enhancement Scale or Bug Severity
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?