-
Notifications
You must be signed in to change notification settings - Fork 8.8k
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
optimize: delete unnecessary cached data #6988
base: 2.x
Are you sure you want to change the base?
optimize: delete unnecessary cached data #6988
Conversation
@@ -71,8 +71,6 @@ public StateMachine getStateMachineById(String stateMachineId) { | |||
stateMachine.setStartState(parsedStatMachine.getStartState()); | |||
stateMachine.getStates().putAll(parsedStatMachine.getStates()); | |||
item.setValue(stateMachine); | |||
stateMachineMapById.put(stateMachine.getName() + "_" + stateMachine.getTenantId(), | |||
item); |
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.
It is not currently in use, but you are not advised to delete the tenant information.
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.
It is not currently in use, but you are not advised to delete the tenant information.
Name+tenantId 是一个隐式的主键,按道理说是可以放在stateMachineMapById中,但是我们这里放进去之后,首先其他地方并没有调用该缓存,并且其他地方缓存数据时,也并没有将Name+tenantId作为隐式主键放到stateMachineMapById中,而是分开存储,只有这个地方单独处理,我觉的应该统一方式,要处理就都处理,要不处理就都不处理,不然容易让人产生困惑
Name+tenantId is an implicit primary key and could theoretically be stored in stateMachineMapById. However, after adding it here, other parts of the system do not call this cache, nor do they use Name+tenantId as an implicit primary key when storing data in stateMachineMapById. Instead, they store the data separately. This is the only place where it is handled individually. I believe the approach should be unified: either handle it everywhere or not handle it at all; otherwise, it may cause confusion.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## 2.x #6988 +/- ##
=========================================
Coverage 52.67% 52.68%
- Complexity 6697 6699 +2
=========================================
Files 1134 1134
Lines 40310 40310
Branches 4722 4722
=========================================
+ Hits 21234 21238 +4
+ Misses 17043 17039 -4
Partials 2033 2033 |
Ⅰ. Describe what this PR did
delete unnecessary cached data
Ⅱ. Does this pull request fix one issue?
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews