JDBC message stores: Rename column to MESSAGE_CONTENT
#10524
Merged
+41
−37
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason for this change is that content in the target DB might not always be a byte array. And we already have an outstanding work for providing JSON format for a message content. Related to: spring-projects#9312
|
After merging this I also will add a Migration Guide note: https://github.com/spring-projects/spring-integration/wiki/Spring-Integration-6.x-to-7.0-Migration-Guide |
cppwfs
requested changes
Oct 21, 2025
|
|
||
| The message stores now use a `MESSAGE_CONTENT` column name for serialized messages instead of `MESSAGE_BYTES` since the content might not always be stored as a byte array. | ||
| All the out-of-the-box SQL schemas have beed changed, too, to rely on the `MESSAGE_CONTENT` name for the respective column in the `INT_MESSAGE` and `INT_CHANNEL_MESSAGE` tables. | ||
| See xref:jdbc/message-store.adoc[] for more information. |
There was a problem hiding this comment.
Do we need to mention that they need to update existing schemas?
There was a problem hiding this comment.
Right. That is what a Migration Guide for.
I don't think the scope of the doc for specific version is a responsibility of such a guidance.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The reason for this change is that content in the target DB might not always be a byte array. And we already have an outstanding work for providing JSON format for a message content.
Related to: #9312
This is mostly an automatic find-n-replace change, therefore not too much to review.