Orientdb: Object API does not propagate cascade save over Set fields

[fuss86]

OrientDB Version: 3.0.21

Java Version: 1.8.0_211-b12

OS: Windows 10

Expected behavior

Update/removal on Set object should work in the cascaded way.

Actual behavior

Update/removal on Set object does not work in the cascaded way.

Steps to reproduce

Thanks to https://github.com/orientechnologies/orientdb/commit/9538c7902c9aa5c5a0713de7a8e53256a02ee914 https://github.com/orientechnologies/orientdb/issues/8272 has been fixed. Unfortunately it does not work in the cascaded way.

Integration test for 3.0.X can be found here.

It also doesn't work in 2.2.X .

[steve-todorov]

@luigidellaquila as the author of the fix for #8272 - would you, perhaps, have any ideas on how this can be fixed or if it's being worked on?

[carlspring]

@luigidellaquila : Any updates on this?

[steve-todorov]

@luigidellaquila, @tglman, @laa guys could we get an update on this issue? :)

[fuss86]

@lvca, any chances to take a look ?

[carlspring]

We would like to upgrade to a newer version of OrientDB, but we're hitting this issue. Any chance you guys could have a look at this and prioritize it?

[fuss86]

I bet they took a veeeerrryyy long vacation time ;)

[carlspring]

@lvca , @luigidellaquila, @tglman, @laa, @wolf4ood ,

Would anyone at all care to give us some sort of update...? Is this being looked at? Are there any known workarounds? Any hints, or advice...?

[luigidellaquila]

Hi guys,

Sorry for the long silence, the Object API for now is low priority in the roadmap.
Unfortunately I do not have a work-around to propose... I'll try to check it when I have a moment

Thanks

Luigi

[carlspring]

@luigidellaquila ,

Any luck with this? Have you had a chance to take a look? :)