[
https://issues.apache.org/jira/browse/JENA-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Soroka closed JENA-1286.
---------------------------
Resolution: Won't Fix
On second thought, I realize that taking advantage of the map implementation in
the default setup for DatasetGraphInMemory would break the encapsulation of
TupleTable<X> behavior. Probably not a good idea.
> Implement DatasetGraph::deleteAny on DatasetGraphInMemory
> ---------------------------------------------------------
>
> Key: JENA-1286
> URL: https://issues.apache.org/jira/browse/JENA-1286
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ
> Reporter: A. Soroka
> Assignee: A. Soroka
> Priority: Minor
>
> DatasetGraph::deleteAny offers opportunity for optimization in
> DatasetGraphInMemory. Currently DatasetGraphInMemory uses the standard impl
> from DatasetGraphBase, but this impl doesn't take advantage of the map-based
> storage in use in DatasetGraphInMemory. We should take advantage of that.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
