Add example demonstrating Nested type serialization issue with custom POJOs #2708
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.
This example demonstrates an issue when using the POJO serializer with nested custom objects.
Test Case
Schema:
POJO:
Usage:
Error
The POJO serializer looks for
getAddressStreet()andgetAddressCity()methods (flattened column names) but the POJO only hasgetAddress()returning anAddressobject. The serializer doesn't traverse nested object graphs.To run the example:
Note
Introduces a nested POJO example to exercise ClickHouse
Nested/Tuple serialization.Addressclass and embeds it inArticleViewEventasaddressarticle_view_event_init.sqlto includeaddress Nested(street String, city String)Main.javato constructAddressand submit it viaPOJO2DbWriterThis demonstrates the serializer behavior with nested custom objects (per PR description).
Written by Cursor Bugbot for commit 3bf8d00. This will update automatically on new commits. Configure here.