This fails with lots of Failed to find avro schema errors in the transformer.
It only works if the config is changed to name: aws_s3access.
Expected Behavior
The name field should not be depended on for determining data schema in the transformer, since it is a human-facing identifier. These messages make it through the data batcher as expected, and they are tagged appropriately with the aws_s3access source type.
Problem
The managed log source type
AWS_S3ACCESS
fails if thename
property in config isn't set toaws_s3access
.Take this example config:
This fails with lots of
Failed to find avro schema
errors in the transformer.It only works if the config is changed to
name: aws_s3access
.Expected Behavior
The
name
field should not be depended on for determining data schema in the transformer, since it is a human-facing identifier. These messages make it through the data batcher as expected, and they are tagged appropriately with theaws_s3access
source type.I expect them to be transformed appropriately.