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

Warning on incompatible multiallelic VCF #3

Open
VelNZ opened this issue Apr 14, 2016 · 1 comment
Open

Warning on incompatible multiallelic VCF #3

VelNZ opened this issue Apr 14, 2016 · 1 comment

Comments

@VelNZ
Copy link

VelNZ commented Apr 14, 2016

Good job putting this together! It's very useful for moving away from the limitations of GEMINI with regard to static files and blobs.

I tried to feed a VCF with multiallelic sites into vcf2db (MySQL mode) and it gave a "Operand should contain 1 column(s)" error. After looking at the line it was complaining about, I found it was a multiallelic site and the error arose because the AF had two values.

It would be useful to detect that the VCF has multiallelic sites and state vcf2db does not support them and direct to vt for decomposition/normalization and exit gracefully.

@brentp
Copy link
Member

brentp commented Apr 14, 2016

thanks for reporting. I punted on this for now because I wanted to decide how to handle it. sqlite is very permissive about what goes in, so it wont give that error (though sqlalchemy likely will). I may use ",".join(alt_list) to allow this and give a warning.
this is vaguely related to #1.

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

No branches or pull requests

2 participants