awslabs / awslabs/aws-lambda-redshift-loader

Trigger LambdaRedshiftLoader on exiting files?

Open
#182 4 comments 0 reactions 1 assignee Claimed by @IanMeyers View on GitHub
Dominant language
JavaScript
Stars
595
Forks
161
PR merge metrics
No merged PRs in 30d

Description

Normally I can trigger a lambda on an existing file by using "Invoke Lambda Function" from AWS tools in visual studio. However, when I attempt to trigger the LambdaRedshiftLoader in this way I get this in cloudwatch:
>2018-12-17T18:04:38.303Z 37ce7250-0226-11e9-95d6-1967f7b75c0c Invalid Event Name s3:ObjectCreated:Put

I have also tried s3:ObjectCreated:Post
I have > 125,000 files I need to reprocess.
I have already deleted all of the relevant entries from LambdaRedshiftBatches and LambdaRedshiftProcessedFiles.
I have set the concurrency on the lambda to 5, so I don't overwhelm DynamoDB or Redshift.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.