-
Notifications
You must be signed in to change notification settings - Fork 53
Fix #27: Remove batching from importers #41
Conversation
I went ahead and removed the Discussion pending of whether this is the best approach (knowing that it is breaking and requires a small change in go-ipfs), or whether in turn we want to make the importer be able to disable batching but leave it enable by default (which would make it compatible, but ihmo just adds more code that shouldn't belong in this module). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, this definitely makes more sense to me but someone else should weigh in on the impact it might have on the go-ipfs
side.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, is there a pr for this on the go-ipfs side?
I'll take care of making a PR on go-ipfs. :) |
See: * ipfs/go-unixfs#41 * ipfs/go-ipld-format#46 License: MIT Signed-off-by: Hector Sanjuan <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The latest modifications to the PR are now rewriting paths with Gx, why?
87ba89b
to
b848469
Compare
sorry, my mess. Fixed @schomatis |
So, if I have approval, I will merge this only when the related changes in go-ipld-format and go-ipfs come through, and all the dependencies are aligned (and rebased to master if needed). For the moment it can stay like this. |
A batching DAG service is forced onto the users of the importers, but they could just wrap the given DAGSerice in the batching one to get the same functionality (remembering to Close it at the end of the proccess). As detailed in #27, the importers should not be making choices about what DAGService is the right one to use and wrapping the given one. This change requires wrapping the DAGService in go-ipfs into ipld.Batch. and closing it when Finishing the adding process.
b848469
to
2d94c3b
Compare
bubbling now. tests good manually. |
Fix ipfs#27: Remove batching from importers This commit was moved from ipfs/go-unixfs@e2784eb
A batching DAG service is forced onto the
users of the importers, but they could just wrap
the given DAGService in the batching one to get the same
functionality (remembering to Close it at the end of the
proccess).
As detailed in #27, the importers should not be making choices
about what DAGService is the right one to use and wrapping the
given one.
This change requires wrapping the DAGService in go-ipfs into
ipld.Batch. and closing it when Finishing the adding process.