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

DAG Import/Export #6870

Closed
Stebalien opened this issue Feb 4, 2020 · 12 comments
Closed

DAG Import/Export #6870

Stebalien opened this issue Feb 4, 2020 · 12 comments
Assignees
Labels
kind/feature A new feature

Comments

@Stebalien
Copy link
Member

We should have DAG Import/Export commands for importing from and exporting to CAR files.

Usage:

> ipfs dag import < my.car
QmRoot1
QmRoot2
> ipfs export SomeSelector > my.car
@Stebalien Stebalien added the kind/feature A new feature label Feb 4, 2020
@Stebalien
Copy link
Member Author

Note: for now, SomeSelector should just be a CID.

@rvagg
Copy link
Member

rvagg commented Mar 2, 2020

@ribasushi

Some test data:

@ribasushi
Copy link
Contributor

ribasushi commented Mar 11, 2020

@Stebalien remaining questions:

@Stebalien
Copy link
Member Author

do we need to somehow integrate https://github.com/ipfs/go-verifcid in go-car ? currently only go-ipfs is "protected" and even there I am not entirely sure ( though tests check out )

The underlying blockstore verifies on read & write, so this shouldn't be necessary.

is api.WithOptions(options.Api.Offline(true)) the proper way to do

Yes.

why are we not supporting pipes: objections to fixing

UX issue around ipfs add -r adding fifos and blocking. But as we discussed on the call, allowing this for direct ipfs add fifo is probably fine.

@pooja
Copy link

pooja commented Apr 3, 2020

Hey all -- is this the correct PR to track for progress on this issue? #7038

Wondering what the overall status is!

@ribasushi
Copy link
Contributor

ribasushi commented Apr 4, 2020

@pooja there are now 3 separate PRs for this, 2 of them ( implementing export ) are ready to go, but became left out of 0.5 due to a number of unrelated troubles with that release. The 3rd one ( implementing import ) is pending a performance regression test for an internal change that had to be made, tentatively by mid-next week, but the import functionality itself is also ready and tested.

@pooja
Copy link

pooja commented Apr 6, 2020 via email

@ribasushi
Copy link
Contributor

Could you drop the links to the 3 relevant PRs?

Apologies, I thought I did 🤦‍♂
Actually it is just PRs now:

@Stebalien Stebalien mentioned this issue Apr 7, 2020
71 tasks
@pooja
Copy link

pooja commented Apr 7, 2020 via email

@ribasushi
Copy link
Contributor

@pooja it all got done, sorry for all the delays: lots of corner cases got ruffled.

@Stebalien
Copy link
Member Author

@ribasushi could you file any issues for remaining pieces (IIRC, you wanted more progress information) and then close this issue?

@ribasushi
Copy link
Contributor

Leftovers tracked at #7141

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature A new feature
Projects
None yet
Development

No branches or pull requests

4 participants