Fix Neptune edge loading by adding S3 notification for output-edges #7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add S3 event notification for output-edges/ prefix - Previously only output/ prefix triggered data loader Lambda - Edge CSV files in output-edges/ were not being loaded into Neptune - This resulted in graphs with vertices but no relationships (0 edges) Fixes: Edge files created by ETL processor were not loaded into Neptune
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Title: Fix Neptune edge loading by adding S3 notification for output-edges
Description:
Problem
Edge CSV files created by the ETL processor in
output-edges/were not being loaded into Neptune, resulting in graphs with vertices but no relationships (0 edges).Root Cause
The S3 event notification only triggered the data loader Lambda for files in the
output/prefix, notoutput-edges/.Solution
Added a second S3 event notification to trigger the data loader Lambda when files are created in
output-edges/.Testing