spring-projects / spring-projects/spring-integration
Add Expression to <resequencer/> to Obtain the SequenceNumber [INT-2624]
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-2624 and commented
Previously (pre #6498) it was possible to specify a custom comparator; but this didn't work. The problem was that a comparator simply provides a way to sort messages in some sequence, but there is no guarantee that the custom comparator uses, or requires a continuous sequence (which is required by the resequencer because it looks for gaps in the sequence), and even if the comparator did, there was no way to supply its location to the resequencer. #6498 removed the custom comparator.
The work around is to set the sequenceNumber header upstream.
It would be convenient to have a sequence-number-expression, or similar, to avoid needing this extra configuration.
Affects: 2.2 M2
Reference URL: http://forum.springsource.org/showthread.php?127532-Bug-with-Resequencer&p=416281&posted=1#post416281
Issue Links:
- #7247 Provide a refactoring Correlation API refactoring to have more abilities to modify and improve components from that API
("depends on") - #6498 Resequencer With Custom Comparator Does Not Release Properly
1 votes, 1 watchers
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 resequencer configuration described in the issue, then read the requirements and context in linked issues #7247 and #6498. Done means the resequencer can obtain its sequence number from a configurable expression, avoiding the need to set the sequenceNumber header upstream.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100