Details
-
Type:
Bug
-
Status: Open
-
Resolution: Unresolved
-
Affects Version/s: BLAZEGRAPH_RELEASE_1_5_1
-
Fix Version/s: BLAZEGRAPH_2_X_BACKLOG
-
Labels:None
Description
There are some methods in AbstractJournal that need to be reviewed such as
@Override
public void delete(final long addr, final IAllocationContext context) {
assertCanWrite();
if(_bufferStrategy instanceof IRWStrategy) {
((IRWStrategy) _bufferStrategy).delete(addr, context);
} else {
_bufferStrategy.delete(addr);
}
}
@Override
public void detachContext(final IAllocationContext context) {
assertCanWrite();
if(_bufferStrategy instanceof IRWStrategy) {
((IRWStrategy) _bufferStrategy).detachContext(context);
}
}
In fact, it is not only the RWStrategy and RWStore that support this protocol. The MemStrategy also supports the protocol and it looks like these methods should be testing on the IAllocationManager.
The impact of this ticket is that the MemStrategy would not correctly support the isolatable journal protocol used by the AbstractTask.
Issue Links
- relates to
-
BLZG-1236
Recycler error in 1.5.1
-
- Done
-