Skip to content

LOGC-41: Add support for nullable fields in ClickHouse #78

Merged
dvasilas merged 4 commits intomainfrom
improvement/LOGC-41
Jan 16, 2026
Merged

LOGC-41: Add support for nullable fields in ClickHouse #78
dvasilas merged 4 commits intomainfrom
improvement/LOGC-41

Conversation

@dvasilas
Copy link
Collaborator

Align ClickHouse schema used in tests and add support for NULL values.

The problem this solves

From AWS documentation:

Any field can be set to - to indicate that the data was unknown or unavailable, or that the field was not applicable to this request.

Bucket logging did not handle this correctly:
When a field was omitted from server-access.log JSON, and FluentBit did not insert a value for it, ClickHouse used a default value (0 for number data types, "" for string, etc)

For example, for a list object operation, object size does not apply and is omitted from the log.
But the final log had object size: 0 instead of -.

@dvasilas dvasilas merged commit f7a64ea into main Jan 16, 2026
6 checks passed
@dvasilas dvasilas deleted the improvement/LOGC-41 branch January 16, 2026 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants