[#SES-637] MemoryStore does not remove expired statements after a remove-only transaction

Issue Details [XML]

Key:	SES-637
Type:	Bug
Status:	Closed
Resolution:	Fixed
Priority:	Major
Assignee:	Arjohn Kampman
Reporter:	Arjohn Kampman
Votes:	0
Watchers:	0

Operations

If you were logged in you would be able to see more operations.

Sesame

MemoryStore does not remove expired statements after a remove-only transaction

Created: 18/Nov/08 11:56 AM Updated: 17/Dec/08 02:05 PM

Component/s:

Memory Sail

Affects Version/s:

2.2.1, 2.1.4, 2.2, 2.1.3, 2.1.2, 2.1.1, 2.1, 2.0.1, 2.0

Fix Version/s:

2.2.2

Description

The MemoryStore records changes to it's set of staments in "snapshot", allowing connections to read statements without being affected by a concurrent connection that modifies the statement set. After an update that changes or removes a statement, the MemoryStore starts a clean-up thread that will remove any deprecated statements from the set as soon as the last connections has finished using the deprecated snapshots. However, this thread doesn't seem to be started when a transaction consists of just removal operations.

All

Comments

Change History

Sort Order:

[ Permlink ]

Comment by Arjohn Kampman [18/Nov/08 12:00 PM]

http://www.openrdf.org/forum/mvnforum/viewthread?thread=1869 might be related.

[ Permlink ]

Comment by Arjohn Kampman [18/Nov/08 12:01 PM]

MemoryStore now also starts the clean-up thread when statements have been removed.