-
-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unsupported data type when parsing optional UUID field in JSON logs #1045
Comments
We might have to look at how dynamic schema behaves - but in this case if you know the schema you're going to ingest, it might be better to use static streams: https://www.parseable.com/docs/server/concepts/ingestion#static |
is there a way to specify an optional field that can be Null or string? From the docs, it looks like theres no notion of an "option" type for a static schema |
I've also tried changing our log formatter so that null fields are removed from the log record, and am getting new errors in the ingestion pod after purging our old log records from S3
|
@sfriedowitz Thanks a lot for reporting the issue! |
I will upgrade our version today and try it out! Will report back, thanks. |
/about
output:Description:
We have a field
uuid
that shows up in our JSON logs, but may not be present for every log event. When it is not present, the logger will output anull
in place of the UUID string. We get this error in our log events which are ingested by FluentBit:Clearly this is an issue with the inferred schema not being able to handle the optional string values for this field. Should we be doing something different, or is this a bug?
The text was updated successfully, but these errors were encountered: