[
https://jira.jboss.org/jira/browse/DNA-40?page=com.atlassian.jira.plugin....
]
Randall Hauch commented on DNA-40:
----------------------------------
Implemented most of the connector behavior (just CopyBranchRequest remains, with a number
of minor tasks). Delete now uses an efficient mechanism for finding subgraphs. The
searches are stores in the database (in a "temporary" area), but this makes
computing the subgraph very efficient (one self-join on the children's table per LEVEL
of subgraph, not per node) and helps to keep most of the information out of memory. The
same mechanism is used for ReadBranchRequest (and will be used for CopyBranchRequest).
A number of methods also use Hibernate bulk HQL statements, which should be faster. (The
subgraph query is just one way in which they're used.)
Note that the "mark and sweep" approach to deleting nodes was abandoned, because
the JCR spec requires that repositories generate delete events for every node that is
deleted, not just for the top node in the subgraph that was deleted.
Persistant storage for information not stored in other repository
sources
-------------------------------------------------------------------------
Key: DNA-40
URL:
https://jira.jboss.org/jira/browse/DNA-40
Project: DNA
Issue Type: Feature Request
Components: Connectors
Reporter: Randall Hauch
Assignee: Randall Hauch
Fix For: 0.4
Create a federation connector that is able to manage information in a relational database
using a DNA-defined schema. This would enable the persistant storage of information that
isn't being managed by other connectors.
Requirements include efficiently storing and accessing large numbers of nodes, large
property values (e.g., Binary values), and large numbers of children on nodes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira