Ticket #687 (closed Enhancement: fixed)

Opened 5 years ago

Last modified 5 years ago

Neo4j Storage: coexistence with non-DM content

Reported by: jri Owned by: jri
Priority: Major Milestone: Release 4.4
Component: DeepaMehta Standard Distribution Version: 4.3
Keywords: Cc: dgf, Malte, carolina
Complexity: 3 Area:
Module: deepamehta-storage-neo4j

Description

DM must not get confused when 3rd-party components store their own (non-DM) data in DM's Neo4j instance, even when this data is connected to DM data via (Neo4j) relationships.

Required in conjunction with Neo4j Spatial, see #633 and #634.

Change History

comment:1 Changed 5 years ago by jri

  • Status changed from new to accepted

comment:2 Changed 5 years ago by Jörg Richter

Neo4j Storage: ignore non-DM content (#687).

Non-DM data of 3rd-party components can coexist with DM data in the same Neo4j instance.

While traversal non-DM nodes are ignored.
DM nodes are recognized by the existence of a node_type property.

See #687.

comment:3 Changed 5 years ago by Jörg Richter

Neo4j Storage: ignore non-DM content (#687).

Non-DM data of 3rd-party components can coexist with DM data in the same Neo4j instance.

While traversal non-DM nodes are ignored.
DM nodes are recognized by the existence of a node_type property.

See #687.

comment:4 Changed 5 years ago by jri

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