spring-projects / spring-projects/spring-integration
Optimize AbstractCorrelatingMessageHandler Lock Keys [INT-2758]
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.6k
- Forks
- 1.2k
- Avg merge
- 17h 48m
- Merged PRs (30d)
- 62
Description
Gary Russell opened INT-2758 and commented
Currently, in order to accommodate the fact the JDBC Message Store uses a UUID representation of the group Id, the ACMH has to use the UUIDConverter to obtain the id of the lock for the group.
This is because the reaper only has the UUID, and not the original group key (correlation id).
When refactoring the JDBC message store to retain the original group key, ensure that the ACMH is also changed, to gain the optimization.
This issue is a sub-task of #6647
Issue Links:
- #6650 Store the Plain Text Group Id instead or in addition to a UUID
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the AbstractCorrelatingMessageHandler and the JDBC message store changes described in #6647 and #6650. Read how UUIDConverter is used for group lock IDs and how the reaper obtains them. Done means the JDBC store retains the original group key and ACMH uses it for lock-key handling without requiring the UUID conversion described here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100