MehtaGraph storage throws Reference error

[jri]

java.lang.IllegalArgumentException: Reference error:
ID 4042 refers to a MehtaEdge when the caller expects a MehtaNode

Solution:

1. There must be 2 distinctive indexes: a node index, and an edge index. The latter one is optional. In any case edge values must NOT be added to the node index.

2. The MehtaGraph? API must provide a getConnectedMehtaObject(s) method (in addition to getConnectedMehtaNode(s) and getConnectedMehtaEdge(s)). The caller must use this method when both types -- nodes AND edges -- are expected on the other side of the edge. This is in particular the case when the Webclient traverses a search result item upwards to find the searchable unit.

See also #384

[Jörg Richter]

MehtaGraph? fix: proper node indexing (#392).

Edge values do not compromise the node index.
For the moment edge values are not indexed at all.

See ticket 392.
See ticket 384.

• Changeset: b8abba88b5e9833138368f93ef0503412214bda7
• URL: ​https://github.com/jri/deepamehta/commit/b8abba88b5e9833138368f93ef0503412214bda7

[Jörg Richter]

MehtaGraph? fix: proper node indexing (#392).

Edge values do not compromise the node index.
For the moment edge values are not indexed at all.

See ticket 392.
See ticket 384.

• Changeset: b8abba88b5e9833138368f93ef0503412214bda7
• URL: ​https://github.com/jri/deepamehta/commit/b8abba88b5e9833138368f93ef0503412214bda7

[Jörg Richter]

MehtaGraph? fix: proper node indexing (#392).

Edge values do not compromise the node index.
For the moment edge values are not indexed at all.

See ticket 392.
See ticket 384.

• Changeset: b8abba88b5e9833138368f93ef0503412214bda7
• URL: ​https://github.com/jri/deepamehta/commit/b8abba88b5e9833138368f93ef0503412214bda7