13.4 Property Name Resolution and Graph Mutations
Property names behave in a similar way as graph names. All property names of a non-published graph are in the session-private namespace. Once a graph is published with PgxGraph.publishWithSnapshots()
or the PgxGraph.publish()
methods, its properties are published as well and their names move into the public namespace.
Once a graph is published, newly created properties will still be private to the session and their names will be in the private namespace. Those properties can be published individually with the Property.publish()
method, as long as no other property with the same name is already published for that graph.
Additionally, new private properties can be created with the same name of an already-published properties (since the names are part of separate namespaces). To handle such situations and retrieve the correct property, the PGX API offers the getVertexProperty(Namespace, String)
and the getEdgeProperty(Namespace, String)
methods, which allow specifying the namespace where the property name should be looked up.
Similar to graphs, if you search a property without specifying the namespace, the private namespace is searched first and if the property is not found, the search proceeds to the public namespace. This case applies for getVertexProperty(String)
or the getEdgeProperty(String)
methods and for PGQL queries.
Likewise, when a mutation on a graph reads or writes a property referred to by name and two properties exist with the same name, the property in the private namespace is selected. To override the default selection, some mutation mechanisms accept a collection of specific Property
objects to be copied into the mutated graph. For example, such mechanism is supported for filter expressions. See Creating Subgraphs for more details.
Parent topic: Namespaces and Sharing