gutting the index engine to make it more friendly for core.async
index engine tests pass, but I'm not clearing chasers up yet
Let's build a new index engine from the ground up in the repl
local event loop?
Thinking about this a bit more
Main indexing process is pretty settled
wrote some thought on chasers
Hooked in the db to the new indexing code
I can do a single pass of indexing
Chaser process should be completely isolated from the overall thing
Shoved the new index engine into its own file
tether up the new index with noticiations to the main database system
we can at least try to pump the indexes occasionally
keep the index engine running until all work is complete, always
uids use index synctags
Nearly all the tests pass, need catch-ups back again
Tests all pass if we're using in-memory, we're not closing writers when replacing indexes though
should pass on travis at least, unless timing issues
yata
core.async for great success