Spike for persistent projections toolkit #1025
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
swistak35
force-pushed
the
rl/persistent-projections
branch
5 times, most recently
from
4bd1c74 to
1c6a673
Compare
Closed
|
I love it! Is there any chance this will get merged or implemented as a feature of RES? |
|
@leifg Yes, definitely, but there are a few different paths we can take from the current state of the spike -- we need to do slightly more research and decide which route we want to take. |
For now only a process which tracks up to which identifier, all transactions has ended.
swistak35
force-pushed
the
rl/persistent-projections
branch
from
f40292e to
1133212
Compare
|
Timed out, might re-use of next spike if that happens. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For now only a process which tracks up to which identifier, all transactions has ended.