Trigger LambdaRedshiftLoader on exiting files?
@IanMeyers is already working on this.
Since Dec 19, 2018.
Assessment
This issue has not been assessed yet.
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.
- Dominant language
- JavaScript
- Stars
- 595
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from awslabs/aws-lambda-redshift-loader
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 32/100
awslabs/aws-lambda-redshift-loader#247 · 3 comments ·
-
Manifest missing file returned in describeBatch.jsMay be free again @IanMeyers claimed this 1390 days ago, and no pull request is open. Open
awslabs/aws-lambda-redshift-loader#244 · 4 comments · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
awslabs/aws-lambda-redshift-loader#239 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
awslabs/aws-lambda-redshift-loader#238 · 1 comment ·
All issues in awslabs/aws-lambda-redshift-loader
Similar issues
-
Language MVP task
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
saayam-for-all/webapp#1914 ·
Maintainers usually reply within 1 day
-
[Bug] Dev image build fails: `npm install` in the root Dockerfile runs out of memory (exit 134)Possibly taken @andest01 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
good first issue hacktoberfest help wanted
Difficulty 2/5 Under an hour Newbie friendliness 76/100
pacocartones/free-llm-api-hub#262 ·
Maintainers usually reply within 1 day
-
agent-task risk:low
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
guyellis/http-status-check#512 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/playwright#43327 ·
Maintainers usually reply within 1 day