Correct eqxsync progress management, rebasing on Equinox.Projection pipeline#21
Merged
Correct eqxsync progress management, rebasing on Equinox.Projection pipeline#21
Conversation
bartelink
added a commit
that referenced
this pull request
May 7, 2019
bartelink
added a commit
that referenced
this pull request
May 7, 2019
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This takes work carried out as part of #16 (which yielded an optimized projection pipeline which lives in the
Equinox.ProjectionNuGet as of2.0.0-preview6) and feeds it into thedotnet new eqxsynctemplate, with the following effects:CosmosIngester), ingestion (viaCosmosIngester, which usesEquinox.Projection.Schedulingto manage the processing async)(Pending testing and load testing, but pretty much code complete at present)