Proposal for Enhanced Graph Cloning in Apache Jena #2169:#2316
Conversation
There was a problem hiding this comment.
Looks great.
One request: Please change the first line of the commit message to
"GH-2169: Enhanced GraphMem Cloning".
Starting with "issue number" is a pattern used to help when reading the commit history.
It looks ready to go to me so it is not a "Proposal" !
|
What is the effect of this on applications using Jena? |
See the issue -- #2169 or the PR code. If the application is using GraphMem's and it has need to copy graphs, then this is made faster. |
- added new interface Copyable<> - implemented Copyable#copy in GraphMem2 all three descendants (Legacy, Fast and Roaring) - extended TripleStore to implement Copyable<> and implemented it in all three descendants (Legacy, Fast and Roaring) - added copy constructors to mem2/collections/*, mem2/store/*/*Bunch, mem2/store/*/*HashMap and mem2/store/*/*Set - added unit tests to keep the test coverage for mem2/** at 100% - added benchmark for GraphMem2#copy - implemented new method G#copy which uses Copyable#copy if the graph implements it, otherwise G#copyGraphSrcToDst is used as fallback. - added a unit test for G#copy
ab02911 to
2d4ca46
Compare
The commit message should be fixed now. |
|
Going into Jena 5.0.0 ... |
GitHub issue resolved #2169
Pull request Description:
By submitting this pull request, I acknowledge that I am making a contribution to the Apache Software Foundation under the terms and conditions of the Contributor's Agreement.
See the Apache Jena "Contributing" guide.