spring-projects / spring-projects/spring-integration
Refactor JdbcMessageStore - Provide separate implementations for MessageStore and MessageGroupStore [INT-2672]
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.6k
- Forks
- 1.2k
- Avg merge
- 17h 48m
- Merged PRs (30d)
- 62
Description
Gunnar Hillert opened INT-2672 and commented
Provide separate implementations for JdbcMessageStore and JdbcMessageGroupStore. Possibly have the JdbcMessageGroupStore extend JdbcMessageStore.
Affects: 2.1.3
Sub-tasks:
-
#6648 Create separate implementations for MessageStore and MessageGroupStore
-
#6649 Add Channel-specific JDBC Message Store
-
#6650 Store the Plain Text Group Id instead or in addition to a UUID
-
#6652 Investigate the possibility of using DB-specific queries
-
#6735 Optimize AbstractCorrelatingMessageHandler Lock Keys
Issue Links:
-
#7069 MongoDb message store deleting messages from wrong group
-
#7200 Deprecate JdbcMessageStore#pollMessageFromGroup in favor of JdbcChannelMessageStore
-
#6587 Doc: Add section that compares the various MessageStore Implementations (pro+cons)
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 by reviewing the JdbcMessageStore, MessageStore, and MessageGroupStore responsibilities described here, then follow sub-task #6648 for the narrower implementation work. Done means separate implementations are provided for MessageStore and MessageGroupStore, with the relationship between them resolved as part of that work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- database
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100