[
https://issues.apache.org/jira/browse/JENA-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041681#comment-15041681
]
A. Soroka edited comment on JENA-624 at 12/4/15 5:02 PM:
---------------------------------------------------------
[~andy.seaborne], now that I'm actually looking at the code, I'm having a hard
time figuring out what would be a good time to do any {{remove}} -ing. The
classes in question never know whether or not a {{Thread}} that has ended a
transaction is gone forever (in which case it is appropriate to {{remove}} the
{{ThreadLocal}} s, or whether it will open a new one (in which case it is not).
Are you suggesting that at all transaction endings, all {{ThreadLocal}} s
should be removed, so for example, instead of setting an {{isInTransaction}}
{{ThreadLocal<Boolean>}} to {{false}}, I should {{remove}} it? If so,
[here|https://github.com/apache/jena/pull/104] is a PR for that.
was (Author: ajs6f):
[~andy.seaborne], now that I'm actually looking at the code, I'm having a hard
time figuring out what would be a good time to do any {{remove}} -ing. The
classes in question never know whether or not a {{Thread}} that has ended a
transaction is gone forever (in which case it is appropriate to {{remove}} the
{{ThreadLocal}} s, or whether it will open a new one (in which case it is not).
Are you suggesting that at all transaction endings, all {{ThreadLocal}} s
should be removed, so for example, instead of setting an {{isInTransaction}}
{{ThreadLocal<Boolean>}} to {{false}}, I should {{remove}} it? If so,
[here:=|https://github.com/apache/jena/pull/104] is a PR for that.
> Develop a new in-memory RDF Dataset implementation
> --------------------------------------------------
>
> Key: JENA-624
> URL: https://issues.apache.org/jira/browse/JENA-624
> Project: Apache Jena
> Issue Type: Improvement
> Reporter: Andy Seaborne
> Assignee: A. Soroka
> Labels: java, linked_data, rdf
>
> The current (Jan 2014) Jena in-memory dataset uses a general purpose
> container that works for any storage technology for graphs together with
> in-memory graphs.
> This project would develop a new implementation design specifically for RDF
> datasets (triples and quads) and efficient SPARQL execution, for example,
> using multi-core parallel operations and/or multi-version concurrent
> datastructures to maximise true parallel operation.
> This is a system project suitable for someone interested in datatbase
> implementation, datastructure design and implementation, operating systems or
> distributed systems.
> Note that TDB can operate in-memory using a simulated disk with
> copy-in/copy-out semantics for disk-level operations. It is for faithful
> testing TDB infrastructure and is not designed performance, general in-memory
> use or use at scale. While lesson may be learnt from that system, TDB
> in-memory is not the answer here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
