You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2019/10/02 13:23:00 UTC

[jira] [Commented] (JENA-1767) Enable clear out of all TDB1 location-related state.

    [ https://issues.apache.org/jira/browse/JENA-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16942808#comment-16942808 ] 

ASF subversion and git services commented on JENA-1767:
-------------------------------------------------------

Commit f6e9b1c85148334959ef07711a553286d86dd44f in jena's branch refs/heads/master from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=f6e9b1c ]

Merge pull request #616 from afs/force-expel

JENA-1767: Release TDB1 database and location state

> Enable clear out of all TDB1 location-related state.
> ----------------------------------------------------
>
>                 Key: JENA-1767
>                 URL: https://issues.apache.org/jira/browse/JENA-1767
>             Project: Apache Jena
>          Issue Type: Bug
>          Components: TDB
>            Reporter: Andy Seaborne
>            Assignee: Andy Seaborne
>            Priority: Major
>             Fix For: 3.13.1
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Jena 3.13.0 TDB1 has caching of DatasetGraphTransaction in TDBMaker (so the same transactional object is used at all times for a given location)
> Previous, the only retained objects were StoreConnections in its cache.
> Tests need to expel all location state.
> Existing tests call StoreConnection.expel so this needs to flush the TDBMaker cache. At the same time (without risk of recusion)
> It would be better to have a TDBInternal operation that controls all this but still retain teh call of StoreConnection.expel.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)