Disable setting the IRI of predicates in Relationship tables of RDFGraphs or make it behave correctly

[semihsalihoglu-uw]

I tried the following query in the UniKG example in the documentation:

MATCH (r:UniKG_r {iri:"http://kuzu.io/rdf-ex#Waterloo"})-[p:UniKG_lt]->(o) 
WHERE p.iri =  "http://kuzu.io/rdf-ex#population" 
SET p.iri = "http://kuzu.io/rdf-ex#population2" 
RETURN r.iri, p.iri, o.iri

This query is trying to set the IRI of the resource node. I got the following output:

--------------------------------------------------
| r.iri                          | p.iri | o.val |
--------------------------------------------------
| http://kuzu.io/rdf-ex#Waterloo |       | 60000 |
--------------------------------------------------

Which already is wrong. But it also did not have any effect, i.e., the IRI stayed the same:

MATCH (r:UniKG_r {iri:"http://kuzu.io/rdf-ex#Waterloo"})-[p:UniKG_lt]->(o) 
WHERE p.iri =  "http://kuzu.io/rdf-ex#population" 
RETURN r.iri, p.iri, o.val;
-----------------------------------------------------------------------------
| r.iri                          | p.iri                            | o.val |
-----------------------------------------------------------------------------
| http://kuzu.io/rdf-ex#Waterloo | http://kuzu.io/rdf-ex#population | 60000 |
-----------------------------------------------------------------------------

The previous IRI is still there. And when I query for all triples, I don't see any triple of Waterloo with predicate http://kuzu.io/rdf-ex#population2.

We should either disable setting iris of predicates or support this so that we implement the right behavior, which is:

1. add the predicate if needed to Resources table
2. set the IRI of the predicate relationship.

[semihsalihoglu-uw]

As per our discussion, let's disable this. I'll document it accordingly.

[andyfengHKU]

Fixed in PR #2786