LOGC-41: Add support for nullable fields in ClickHouse #78
Merged
Conversation
Sync changes from S3C-10746.
All formatters output "-" for NULL values.
fredmnl
approved these changes
Jan 13, 2026
jonathan-gramain
approved these changes
Jan 14, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Align ClickHouse schema used in tests and add support for NULL values.
The problem this solves
From AWS documentation:
Bucket logging did not handle this correctly:
When a field was omitted from
server-access.logJSON, and FluentBit did not insert a value for it, ClickHouse used a default value (0for number data types,""for string, etc)For example, for a
list objectoperation,object sizedoes not apply and is omitted from the log.But the final log had
object size: 0instead of-.