Skip to content
This repository has been archived by the owner on Apr 8, 2019. It is now read-only.

issue import in MongoDB from subset 254 #3

Open
mcourtot opened this issue Sep 5, 2017 · 4 comments
Open

issue import in MongoDB from subset 254 #3

mcourtot opened this issue Sep 5, 2017 · 4 comments

Comments

@mcourtot
Copy link

mcourtot commented Sep 5, 2017

I think the data for subset 254 was not exported using a jsonArray, and consequently loading using the provided import script fails. Removing the --jsonArray allows import to go through.

Note: for subset 347 the option --jsonArray is needed for loading.

@mbaudis
Copy link
Collaborator

mbaudis commented Sep 5, 2017

@mcourtot Thanks for checking. It is on the action list for Thursday to have all examples working (right, @KyleGao ?).

@mcourtot
Copy link
Author

mcourtot commented Sep 5, 2017

Just ran the notebooks and they all work fine - great work @KyleGao!- sorry if that was unclear. It's just the initial data loading step from the json in the zip into MongoDB.
Thanks!

@KyleGao
Copy link
Collaborator

KyleGao commented Sep 5, 2017

Thank you @mcourtot . I will check the data sets, make sure they are all generated and can be imported with the same protocol.
I will demonstrate use cases on Thursday. @mbaudis

@KyleGao
Copy link
Collaborator

KyleGao commented Sep 6, 2017

Subset 254 is an early version, I have removed it. Subset 347 is a better and later version.
I have also put up the latest version Subset_347_multi, it contains data in multiple genome editions.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants