[JBoss JIRA] Commented: (DNA-40) Create connector to store any content in a relational database
by Randall Hauch (JIRA)
[ https://jira.jboss.org/jira/browse/DNA-40?page=com.atlassian.jira.plugin.... ]
Randall Hauch commented on DNA-40:
----------------------------------
Added to the JPA connector support for referential integrity (which is optional). References that are values in properties are now tracked in the database, where each reference record maps the UUID of the node containing the reference to the UUID of the node being referenced. Note that this table does not maintain which property contains the reference, which is not required to manage dependencies.
Finally, these references are checked upon closing the BasicRequestProcessor to catch any operations that remove any nodes that are still being referenced by other nodes.
> Create connector to store any content in a relational database
> --------------------------------------------------------------
>
> 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
17 years, 4 months
[JBoss JIRA] Created: (DNA-250) Creating a path from a parent path and a segment is not fast
by Randall Hauch (JIRA)
Creating a path from a parent path and a segment is not fast
------------------------------------------------------------
Key: DNA-250
URL: https://jira.jboss.org/jira/browse/DNA-250
Project: DNA
Issue Type: Bug
Components: Graph
Affects Versions: 0.3
Reporter: Randall Hauch
Assignee: Randall Hauch
Fix For: 0.3
Currently, we only have one implementation of Path, and each instance contains a list of the Path.Segment instances in the path. Although the actual Path.Segment instances are shared when creating a path using a parent path, the actual list is not shared. And this means new allocation for each Path. This could be more efficient, especially since creating a path from a parent path and a name is perhaps one of the most frequently used methods.
We probably need an implementation of Path that contains a name plus a reference to a parent. This would have a smaller memory footprint as well as be faster to create.
--
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
17 years, 4 months
[JBoss JIRA] Commented: (DNA-40) Create connector to store any content in a relational database
by Randall Hauch (JIRA)
[ https://jira.jboss.org/jira/browse/DNA-40?page=com.atlassian.jira.plugin.... ]
Randall Hauch commented on DNA-40:
----------------------------------
Changed the Graph API to improve the methods of getting blocks of children, including adding a new technique for getting the 'n' children that follow a previously-returned sibling. This did change the API, but these were methods that were not used except in test cases.
Also implemented in the JPA Store connector the process methods for ReadBlockOfChildrenRequest and ReadNextBlockOfChildrenRequest, utilizing efficient database operations for these methods to efficiently find and return the block of children.
> Create connector to store any content in a relational database
> --------------------------------------------------------------
>
> 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
17 years, 4 months
[JBoss JIRA] Created: (DNA-265) Improve the Graph API's methods for returning blocks of children
by Randall Hauch (JIRA)
Improve the Graph API's methods for returning blocks of children
----------------------------------------------------------------
Key: DNA-265
URL: https://jira.jboss.org/jira/browse/DNA-265
Project: DNA
Issue Type: Feature Request
Components: API, Graph
Affects Versions: 0.3
Reporter: Randall Hauch
Assignee: Randall Hauch
Priority: Minor
Fix For: 0.4
The Graph API has several methods for getting a subset (or "block") of children by specifying the parent, starting index, and child. This is useful when a graph client is paging through the children. However, the Graph API methods to do this are less than ideal and don't make for readable code. Plus, there is a use case when the client doesn't want to specify the index, but rather they want to specify the last child that they read. This may be more appealing to some clients for cases when the children are being modified, and the indexes change in between calls to read blocks.
The Graph API should be changed to make getting children more closely aligned with the method to get all children, so that developers can decide after they add the "getChildren()." call, letting the IDE show the different options. Also, the API should supporting getting n children after a previously-retrieved sibling.
Here are some examples of what the new API should look like. This line:
graph.getChildren().of(parent);
gets all children of the 'parent' node (where 'parent' can be a string path, Path, Location, UUID, or identification Property objects). This line:
graph.getChildren().inBlockOf(10).startingAt(50).under(parent);
gets up to 10 children under a parent node, starting at the 51st child (remember, indexes are 0-based). And this line:
graph.getChildren().inBlockOf(10).startingAfter(sibling);
gets up to 10 children that immediately follow the 'sibling' node. Here, 'sibling' can be a string path, Path, Location, UUID, or identification Property objects, but will often be the actual Location returned from a previous call.
--
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
17 years, 4 months
[JBoss JIRA] Commented: (DNA-36) Federate content from SVN
by Randall Hauch (JIRA)
[ https://jira.jboss.org/jira/browse/DNA-36?page=com.atlassian.jira.plugin.... ]
Randall Hauch commented on DNA-36:
----------------------------------
Changed the way the local repository is created to better match how Hudson works (hopefully). Also changed to use the FileUtil.deletemethod, and moved the copy functionality into FileUtil. Finally, changed the asserts in the SVNRepositoryConnection constructor to be arg checks; this is more testable (as unit tests should not be expecting AssertionError, as then it is not possible to run the unit tests against the code with asserts removed.
> Federate content from SVN
> -------------------------
>
> Key: DNA-36
> URL: https://jira.jboss.org/jira/browse/DNA-36
> Project: DNA
> Issue Type: Feature Request
> Components: Connectors
> Affects Versions: 0.4
> Reporter: Randall Hauch
> Assignee: Serge Emmanuel Pagop
> Priority: Minor
> Fix For: 0.4
>
>
> Create a connector for the federation engine that contributes and exposes content stored in a source control management (SCM) system into the federated repository. This would enable integration of files managed by SVN (or CVS, etc.) to be accessible via JCR.
--
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
17 years, 4 months