Ticket #392 (closed Defect: fixed)

Opened 8 years ago

Last modified 8 years ago

MehtaGraph storage throws Reference error

Reported by: jri Owned by: jri
Priority: Blocker Milestone: Release 4.1
Component: DeepaMehta Standard Distribution Version: 4.0.13
Keywords: Cc: dgf, Malte
Complexity: 5 Area:
Module:

Description

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.
  1. 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

Change History

comment:1 Changed 8 years ago by jri

  • Status changed from new to accepted

comment:2 Changed 8 years ago by 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.

comment:3 Changed 8 years ago by 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.

comment:4 Changed 8 years ago by 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.

comment:5 Changed 8 years ago by jri

  • Status changed from accepted to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.