Add a MapView for Chronicle Queue
Closed this issue · 3 comments
The MapView would have a key and an index to the queue entry.
Add the option to migrate values after a roll. e.g. after a cycle roll, migrate all keys older than a cycle (the one before the previous cycle)
Is this not just chronicle-journal, and as such, I think, this change should go in its own project, perhaps an enterprise project at that. In other words, I don think we should bloat chronicle queue with this )
From a design point of view, I don't think queue should depend on engine.
This could be added to engine as we should only do a trivial implementation
in the OS version.
A more efficient native version should be in something like Journal +
closed source.
On 23 Sep 2016 11:46, "Rob Austin" notifications@github.com wrote:
Is this not just chronicle-journal, and as such, I think, this change
should go in its own project, perhaps an enterprise project at that. In
other words, I don think we should bloat chronicle queue with this )—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#12 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABBU8QyKpg1nI98InN2PjVur9vpdyKPsks5qs_RJgaJpZM4JThxw
.
done see tests - QueueAsMapView and for replication ( in enterprise queue ) - software.chronicle.enterprise.queue.ReplicatedQueueAsMapViewTest