optimize: add support for Jackson serialization and deserialization of PostgreSQL array types #7669
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.
Ⅰ. Describe what this PR did
1. Problem Background
When the database is PostgreSQL, the table contains an array type.
When using Seata AT mode, a JSON deserialization exception is thrown when a service failure triggers a global transaction rollback.
2. Problem Analysis
Seata Array Handling Mechanism:
org.apache.seata.rm.datasource.sql.serial.SerialArray
objects.Jackson Serialization Configuration:
JacksonUndoLogParser
has enableDefaultTyping enabled for type information processing.Deserialization Conflict:
3. Solution:
JacksonUndoLogParser
to ensure:Ⅱ. Does this pull request fix one issue?
fixes #7661
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
testSerializeAndDeserializeSerialArray()
testSerializeAndDeserializeSerialArrayWithNulls()
mvn clean test
Ⅴ. Special notes for reviews
ps: I also changed the access modifier of DmdbTimestampDeserializer to private.❤️