|
About the AWS batch pipeline category
|
1
|
April 12, 2016
|
|
Disc usage during EMR stage
|
3
|
August 8, 2019
|
|
Schema mismatch while creating atomic tables in Redshift
|
4
|
July 23, 2019
|
|
EMR failing in enrich step
|
8
|
June 9, 2019
|
|
Monitoring of snowplow
|
11
|
May 29, 2019
|
|
Snowplow-emr-etlrunner exit code 3 on empty input bucket
|
4
|
April 19, 2019
|
|
Shred step just started failing (R97)
|
2
|
March 19, 2019
|
|
Trying to copy non-existent file: Elasticity S3DistCp Step: Raw S3 -> Raw HDFS
|
7
|
January 8, 2019
|
|
Error occured at emretlrunner
|
1
|
December 24, 2018
|
|
Contract violation for return value
|
3
|
December 8, 2018
|
|
Help with provisioning rdb loader
|
9
|
November 10, 2018
|
|
EmrEtlRunner fails during raw staging S3 step
|
5
|
November 8, 2018
|
|
Shredded type not loading into Redshift
|
2
|
November 8, 2018
|
|
Snowplow ETL on AWS EMR hangs
|
2
|
October 26, 2018
|
|
LoadError after upgrading to R109
|
3
|
October 10, 2018
|
|
Raw events in gzip
|
2
|
October 9, 2018
|
|
Emr-etl-runner works with LZO but not with GZ
|
5
|
October 9, 2018
|
|
ArgumentError (AWS EMR API Error (ExpiredTokenException): The security token included in the request is expired)
|
2
|
October 6, 2018
|
|
Storage loader Failure with an unwanted json schema
|
3
|
September 29, 2018
|
|
EMR Additional Security Groups
|
3
|
September 20, 2018
|
|
Batch pipeline upgrade from R106 to R109 failed
|
2
|
September 12, 2018
|
|
Upgrade snowplow from R98 to R109
|
3
|
September 7, 2018
|
|
Disable shredding on EMR
|
4
|
September 5, 2018
|
|
Archive shred step is not working
|
2
|
September 4, 2018
|
|
Recommended ec2 instances for EMR ETL Runner in 2018
|
3
|
September 4, 2018
|
|
Random string populated in user_id in atomic.events
|
2
|
August 30, 2018
|
|
[SOLVED] S3DistCp is not deleting files on the etl first step
|
5
|
August 10, 2018
|
|
Empty s3 shredded logs after successful EmrEtlRunner job
|
6
|
August 9, 2018
|
|
Exception in emr step of loading data in redshift
|
9
|
July 31, 2018
|
|
Intermittent EMR failure: Unable to find a region via the region provider chain
|
4
|
July 3, 2018
|
