-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Closed as not planned
Labels
Stalearea/querylangIssues related to the query language specification and implementation.Issues related to the query language specification and implementation.dgraphIssue or PR created by an internal Dgraph contributor.Issue or PR created by an internal Dgraph contributor.exp/expertDeeply technical issue not recommended to beginners.Deeply technical issue not recommended to beginners.kind/enhancementSomething could be better.Something could be better.
Description
What you wanted to do
A massive upsert (milions of nodes).
Why that wasn't great, with examples
All massive upserts take some time to execute. The massive upsert works fine, but there's no visual reference during the process if it is going well or not. Sometimes Ratel could fail visually or the Browser (for some reason) and We're not sure if the Big Upsert was executed or still executing.
We could have two types of reference for this. Could be API responses (if possible) sending percentage values and a log in the Alpha's log terminal. The log would start to appear only if the transaction takes more time than usual.
Observation
This probably would be done after we have a Query Planner.
erhlee-bird
Metadata
Metadata
Assignees
Labels
Stalearea/querylangIssues related to the query language specification and implementation.Issues related to the query language specification and implementation.dgraphIssue or PR created by an internal Dgraph contributor.Issue or PR created by an internal Dgraph contributor.exp/expertDeeply technical issue not recommended to beginners.Deeply technical issue not recommended to beginners.kind/enhancementSomething could be better.Something could be better.