Support cluster selection for DELETE commands

[StarpTech]

OrientDB Version, operating system, or hardware.

• v2.0 SNAPSHOT[ ] - .18[ X] .17[ X] .16[ ] .15[ ] .14[ ] .13[ ] .12[ ] .11[ ] .10[ ] .9[ ] .8[ ] .7[ ] .6[ ] .5[ ] .4[ ] .3[ ] .2[ ] .1[ ] .0[ ]
• v2.1 SNAPSHOT[ ] - .16[X ] .15[ X] .14[ X] .13[ ] .12[ ] .11[ ] .10[ ] .9[ ] .8[ ] .7[ ] .6[ ] .5[ ] .4[ ] .3[ ] .2[ ] .1[ ] .0[ ]
• v2.2 SNAPSHOT[ ] - .rc1[X ] .beta2[ X] .beta1[X ]

All Versions!

Operating System

• Linux
• MacOSX
• Windows
• Other Unix
• Other, name?

Expected behavior and actual behavior

With regard to the Distribution strategy of orientdb it must be possible to select a cluster to avoid a scan through all irrelevant clusters.

Expected sql support:

DELETE EDGE <class> CLUSTER <cluster>|[<cluster>,...] WHERE <where>

Steps to reproduce the problem

throws an exception:

DELETE EDGE <class> CLUSTER <cluster>|[<cluster>,...] WHERE <where>

[smolinari]

Hey Dustin,

Doesn't the simpler command DROP CLUSTER <cluster-name>|<cluster-id> work?

Scott

[StarpTech]

Hi @smolinari I think yes but it has nothing to do with it. I want to remove a record from a specific cluster.

[smolinari]

Oh boy. Sorry about that. Don't know what I was thinking......

Scott

[lvca]

@StarpTech you can always delete edges by using rids. This is fast and is executed only by the servers that have the record:

DELETE EDGE #13:4343

or

DELETE EDGE [#13:4343, #134:434, #32:965976]

[lvca]

I've just checked and DELETE EDGE command is not optimized for this, but DELETE VERTEX contains it. I'm converting this in an enhancement.

[lvca]

Implemented in 2.2.x and develop branches.

[StarpTech]

Hi @lvca thank you but can you port it to the 2.1.x series? You know my issues with switching to the 2.2.x series. thank you.

[VillHub]

DELETE EDGE edgename
not working when E is orestricted subclass
issue #6425