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

Fixing graphdb to mongodb #204

Merged
merged 12 commits into from
Jun 14, 2024
Merged

Fixing graphdb to mongodb #204

merged 12 commits into from
Jun 14, 2024

Conversation

jt-dd
Copy link
Contributor

@jt-dd jt-dd commented Jun 12, 2024

With KHaaS, rehydrating the data from the dump:

  • Checking if the data is already ingested (is there at least one data with run_id / cluster present in Janusgraph)
  • Checking if there is data in the MongoDB (looping over the collection to find assets with run_id / cluster)
    • If found, deleting the data, to rerun the ingestion process.

Added a system-test to simulate GRPC ingestion.

@jt-dd jt-dd marked this pull request as ready for review June 14, 2024 10:06
@jt-dd jt-dd requested a review from a team as a code owner June 14, 2024 10:06
edznux-dd
edznux-dd previously approved these changes Jun 14, 2024
edznux-dd
edznux-dd previously approved these changes Jun 14, 2024
@jt-dd jt-dd enabled auto-merge (squash) June 14, 2024 12:08
@jt-dd jt-dd disabled auto-merge June 14, 2024 12:24
@jt-dd jt-dd merged commit 61570bc into main Jun 14, 2024
7 checks passed
@jt-dd jt-dd deleted the jt-dd/fix-rehydrate-data branch June 14, 2024 12:26
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

Successfully merging this pull request may close these issues.

2 participants