java.lang.ClassCastException: com.orientechnologies.common.collection.OMultiCollectionIterator cannot be cast to com.tinkerpop.blueprints.impls.orient.OrientEdge [ONetworkProtocolHttpDb]
I would hope something like that would delete the in and outs
However, not using LWE, I can do something like
delete edge is_genre where out=#13:53
which I can only assume assumes you saying that the SQL is tricky to write for LWE's.
How much practically does LWE's save in both memory and query path costs? I won't be working on massive amounts of data, can probably assume around 150k films, each with several genre categories, say 2.5, so for estimations, around 375k edges (there's only 20 genres though so each genre will be have 1000s edges)
I hope to be running some complex queries utilising the genre links, hence assumed LWE would be best option (I also have no need to label the edges), but if you feel non-LWE will not impact performance noticeably then I will turn them off