Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implementing Bidirectional Edge Creation in csv-to-neptune-bulk-format #346

Open
adleite opened this issue Jun 21, 2024 · 0 comments
Open

Comments

@adleite
Copy link

adleite commented Jun 21, 2024

Hello,

I recently started using csv-to-neptune-bulk-format after finding that my custom solution (using Gremlin query strings by row) didn't deliver the performance benefits of a bulk loader as promised. One improvement I believe could enhance the converter tool is the capability to utilize existing vertex IDs from Neptune. This would allow for creating edges based on data from both ends of the edge solving late arriving data issues.

For instance, consider the scenario with Consumer and Orders data. The Consumer dataset contains consumer information but lacks order details. As a result, we cannot define "Consumer_to_Order" edges because we don't have visibility into which Orders each Consumer has in Neptune. These edges can only be established once we receive the Order data.

I am planning to implement this enhancement as a fork of the tool. Do you think it would be beneficial to merge this back into the main repository once completed?

Thanks in advance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant