Will it be possible to assign nodes multiple Labels?

[automagic]

For example (from the OpenCypher spec):

(a:User:Admin)-[]->(b)

[Halkrine]

Maybe it doesn't supported yet.

Another way that question is here I think.

select * from cypher('test_graph', $$ match(a)-[]->(b) where label(n) = 'User' or label(n) = 'Admin' return n $$) as (n agtype) ;

[sserdyukov]

In v1.1.0 it is still not supported.
Any ideas how to implement nodes hierarchy without having multiple labels per node?
(E.g. node may have both labels "Asset" and "File", and one can query either all assets or all files )

[jrgemignani]

@sserdyukov @automagic Currently AGE does not support multiple labels. It was a design decision very early on to only have 1 label per vertex or edge; this was due to performance considerations. We are currently forming a project to look into the feasibility of changing this.

[sserdyukov]

@jrgemignani
Thank you for the answer! Seems I have a workaround for now, so the performance considerations are more important.

Age project is very promising. Are you planning any performance benchmarks for Age in terms of read/write/aggregate etc.? Any expectations on the potential limits of loaded data volumes?

And maybe comparisons to some of the currently existing solutions like Neo4j, ArangoDB, OrientDB, ArcadeDB?

[jrgemignani]

I know that some are looking into these as we speak. But, that is all that I can say atm.

[DamilShahzad7]

Apache AGE does not have native support for assigning multiple labels to nodes.
In the property graph model, nodes typically have a single label or type assigned to them, each node can only have one label associated with it

[jberzy]

Is it possible that we can address the multiple labels feature by utilizing postgres views? In other words, allow age to register views that return the same shape as standard node/edge tables in the catalogue.

Another benefit of this feature is we'd have the ability to adapt relational data without explicitly converting the data to nodes/edges. Kind of like a dynamic graph that can be backed up by other data sources...

[jberzy]

FYI - I'm creating a POC for the idea. You can find the WIP PR here: #1735

You'd be able to create a view that unions multiple Node tables and register that view as a virtual vertex/edge with create_computed_vlabel or create_computed_elabel.