Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

No batchId in LambdaRedshiftProcessedFiles

Open
#126 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, javascript

Research direction

Start by tracing how LambdaRedshiftProcessedFiles records are created and how batchId is assigned. Investigate the 242 records without a batchId, determine whether those files were processed, and document the confirmed behavior or failure condition.

Written by the indexing model from the issue text.

Description

I have copied roughly 700 files to S3. Most of the files are processed as expected. However, LambdaRedshiftProcessedFiles contains 242 files without a batchId.

Does that mean that they were not really processed? What is happening exactly?

Dominant language
JavaScript
Stars
595
Forks
161
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from awslabs/aws-lambda-redshift-loader

All issues in awslabs/aws-lambda-redshift-loader

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.