Michel, thank you very much for your prompt response. I’m wondering if you think query performance would be better if we were to directly query on the node UID vs. on the indexed string “software engineer”.
This gets to a related question. My understanding is that in DQL, you can’t specify your own unique node UIDs (unless you ingest the entire graph at once, in which case you could use the same “blank” nodes). In the above case, assuming there is a performance benefit to querying on the UID, if the UIDs were deterministic, for example, as in a pure RDF database, the subject or object would be a URL, so we’d query for the node “http://foo.org/jobTitle/softwareEngineer” instead of a string lookup on “software engineer”. This is especially the case since we basically have an enum of jobTitles, so it would be much more efficient for us to create our own UIDs for each of them, than to have to do a lookup each time we want to add an edge pointing to a jobTitle of “software engineer” or another job title. Even if we cache the UID values in our code, it would be much easier to use custom UIDs if possible, so in that case we could hard-code UIDs and even be consistent across multiple dgraph clusters (such as different test and production clusters). Is there a way to use a custom UID in DQL?
Thank you!!