Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue #337 #345

Merged
merged 4 commits into from
Sep 17, 2020
Merged

Issue #337 #345

merged 4 commits into from
Sep 17, 2020

Conversation

jacksontj
Copy link
Owner

No description provided.

The majority of times there are holes in the data a single downstream
has a hole but the other has the data; in that case since we have the
data in memory there is no reason to chose the "worse" data and merge
from there.

This has the caveat that this is done on a per-merge basis; so if there
are N servers and the first 2 return with holes they will be merged; but
due to anti-affinity if there is any server with no hole it will always
have more points than a merged series.
@jacksontj jacksontj marked this pull request as ready for review September 15, 2020 23:28
@jacksontj jacksontj merged commit 77f24fe into master Sep 17, 2020
@jacksontj jacksontj deleted the issue_337 branch September 17, 2020 05:29
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.

1 participant