-
Notifications
You must be signed in to change notification settings - Fork 308
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
refactor RDD loading; explicitly load alignments #468
Conversation
+1, I think this is a good idea. We should extend it to variants as well, at a later time. |
Test FAILed. Build result: FAILUREGitHub pull request #468 of commit b9b4718 automatically merged.[EnvInject] - Loading node environment variables.Building remotely on amp-jenkins-slave-01 (centos) in workspace /home/jenkins/workspace/ADAM-prb > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/bigdatagenomics/adam.git # timeout=10Fetching upstream changes from https://github.com/bigdatagenomics/adam.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/bigdatagenomics/adam.git +refs/pull/:refs/remotes/origin/pr/ > git rev-parse origin/pr/468/merge^{commit} # timeout=10Checking out Revision 81f2b1f (detached) > git config core.sparsecheckout # timeout=10 > git checkout -f 81f2b1f > git rev-list a34074082d54668273cacb5528d8aaed1b9c6ea8 # timeout=10Triggering ADAM-prb » 1.0.4,centosTriggering ADAM-prb » 2.2.0,centosTriggering ADAM-prb » 2.3.0,centosADAM-prb » 1.0.4,centos completed with result FAILUREADAM-prb » 2.2.0,centos completed with result FAILUREADAM-prb » 2.3.0,centos completed with result FAILURETest FAILed. |
Jenkins retest this. |
@massie do you know why Jenkins failed? or why the retest? (I thought tests were passing for me locally; trying again now as well) |
@ryan-williams it looks like the SAM loading tests are failing:
|
yea seems real, let me look, I swear they were passing very shortly before I pushed |
b9b4718
to
187acbd
Compare
cool, that should have fixed it, just needed to bring |
Test PASSed. |
There’s really not a case where we are loading a generic Parquet file of SpecificRecords whose type we don’t have a strong requirement about; on the other hand, there is a case where we know what type we want (AlignmentRecord) but don’t know which code path to read it in via (sam, bam, ifq, fq, parquet, …). Here I’ve made the caller explicitly specify if it wants AlignmentRecords (which it was previously doing by labeling the return value), but wants to benefit from the smarts around file-extension inference. Parquet reads with a known type can still go through one place so that we can continue to benefit from that code not needing to be duplicated, by only relying on SpecificRecord.
bump! this good to go? |
Ah, yes! Thanks for the ping. Can you rebase? I'll merge once rebased. |
187acbd
to
66dd5e7
Compare
I believe it is now rebased |
refactor RDD loading; explicitly load alignments
Merged! Thanks @ryan-williams! |
Test PASSed. |
There’s really not a case where we are loading a generic Parquet file of
SpecificRecords whose type we don’t have a strong requirement about;
on the other hand, there is a case where we know what type we want
(AlignmentRecord) but don’t know which code path to read it in via (sam,
bam, ifq, fq, parquet, …).
Here I’ve made the caller explicitly specify if it wants
AlignmentRecords (which it was previously doing by labeling the return
value), but wants to benefit from the smarts around file-extension
inference.
Parquet reads with a known type can still go through one place so that
we can continue to benefit from that code not needing to be duplicated,
by only relying on SpecificRecord.