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

Sync Fork from Upstream Repo #67

Merged
merged 3 commits into from Jan 11, 2020
Merged

Sync Fork from Upstream Repo #67

merged 3 commits into from Jan 11, 2020

Conversation

sthagen
Copy link
Owner

@sthagen sthagen commented Jan 11, 2020

No description provided.

elprans and others added 3 commits January 10, 2020 21:52
Since type variants are ephemeral, the only inherited ref
propagation that makes sense is pointers, everything else
should not propagate.

Fixes: #1005
There are two goals that caused this change:

* Simplify dump/restore tools implementation. Essentially, with this
  change they are no longer unpacking dump messages. The only thing that
  the dump tool is doing is receiving packages, hashing them with sha1
  and storing them on disk.

* The restore tool reads the dump data from the disk and simply
  forwards it to the server (with minimal setup).  99% of the actual
  logic is implemented on the server now.

* The dump block message is now generic -- all data is stored using
  headers.  That allows us to introduce more data blocks kinds in the
  future keeping the same dump/restore cli implementation.

* The new protocol for dump is compatible with streaming.
@sthagen sthagen merged commit 709d397 into sthagen:master Jan 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants