amaster507
(Anthony Master)
December 17, 2021, 3:57am
6
You want my thorough thoughts on the subject of types then check out:
I have read in detail your other latest blog post:
It was so mesmerizing. Your engineering mind is exceptional!!
The optimization improvements are terrific for a database that already touts ingestion speeds keeping up with major databases.
And then I saw the type problem, and you confirmed the problem with indexes. So, what if, types weren’t indexes, they were edges??
I can hear Chewxy correcting me already, that everything is already an edge, it is turtles all the way do…
Correct, uid is reserved but not id.
Curious on how you will be testing 21.12 I figure an export/import. And then I wonder that since the differing nodes are identical if it is not an overflow problem somewhere. I really wish someone from the @core-devs would chime in here. This is above my pay grade (sarcastic idiom).
What I would like to know is:
Is there any difference in storage on disk for the dgraph.type predicate vs any other predicate?
Since this type(Foo) function is equivalent to a…
And more specifically to answer
Juri:
But doing if to check every value if it is a restaurant, is more slowly, than having 3 indexes? because checking something through indexes is faster than checking it through filters/if-checks ? or not?
Maybe I didn’t explain it good enough, but I am getting done for the night, I’ve wasted too many hours tonight on Dgraph.
Doing the IF check with a single index (would be better with an edge ^^^ maybe ?) is the only way to do it because it is illogical to build an index across three types that may no coexist.
1 Like