-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Scala Common Enrich: update CloudfrontAccessLogAdapter to support newer 26 field format #3816
Comments
mdemri
changed the title
Spark enrich failed while processing Cloudfront Logs
Spark (common) enrich failed while processing Cloudfront Logs
Jun 20, 2018
alexanderdean
changed the title
Spark (common) enrich failed while processing Cloudfront Logs
Scala Common Enrich: update CloudfrontAccessLogAdapter to support newer 26 field format
Jun 20, 2018
Updated ticket name as there is a newer format. But @mdemri - you are using the wrong configuration setting for the CloudFront collector. Please raise a Discourse thread and we can help: |
Thanks for the report @mdemri 👍 , feel free to open a PR 👍 |
oguzhanunlu
pushed a commit
to snowplow/common-enrich
that referenced
this issue
May 29, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While running EMR ETL runner with Cloudfront collector,
The enrichment phase could not parse the logs, since it contains 26 fields.
Log file format actually contains 26 fields, https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/AccessLogs.html#LogFileFormat
But the common enrich code doesn't support it (supports only 24 fields)
snowplow/3-enrich/scala-common-enrich/src/main/scala/com.snowplowanalytics.snowplow.enrich/common/adapters/registry/CloudfrontAccessLogAdapter.scala
Line 100 in 9904386
The last two fields in the CF logs are redundent for this case.
The text was updated successfully, but these errors were encountered: