Skip to content

Conversation

@sikefield3
Copy link

THIS IS A DRAFT! DO NOT MERGE!

This code is work in progress and I might still have some misconceptions.

The main thing happens in RocksStorage::postRemoveAtom in opencog/persist/rocks/RocksIO.cc: Look if we have marked an entry in Rocks (atm still '-2', but this can be changed as mentioned earlier). Then check in AS if it is absent and delete if necessary.

This is not meant to compile yet and some smaller parts might still be missing...

@linas
Copy link
Member

linas commented Apr 26, 2024

I n this comment: #15 (comment) I'm trying to say that you do not need to actually write the "-2" out to the database. That is because the pre-remove and the post-remove calls will come, one right after the other, in the same thread. You'll always know exactly which atom it is, and in what state it is in, so you don't need to write anything out.

Did I miss something?

@sikefield3
Copy link
Author

Please note my answer

@linas
Copy link
Member

linas commented Dec 10, 2025

The design driving this is described in issue #15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants