-
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
Unable to save GenomicRDDs after a join. #1576
Milestone
Comments
fnothaft
added a commit
to fnothaft/adam
that referenced
this issue
Jul 11, 2017
2 tasks
fnothaft
added a commit
to fnothaft/adam
that referenced
this issue
Jul 11, 2017
fnothaft
added a commit
to fnothaft/adam
that referenced
this issue
Jul 12, 2017
fnothaft
added a commit
to fnothaft/adam
that referenced
this issue
Jul 13, 2017
fnothaft
added a commit
to fnothaft/adam
that referenced
this issue
Jul 17, 2017
heuermh
pushed a commit
that referenced
this issue
Jul 17, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are two things at work here:
1.) We are upcasting to
GenomicRDD
after a join, which does not have any save functionality attached.2.)
GenericGenomicRDD
extendsGenomicRDD
, but does not have any save functionality attached.I think it would be ok to create a
GenomicRDD
that is specific to the result joins and other set operations, mimicking thePairRDDFunctions
in Spark. I don't see it as a problem for the user to be exposed to aGenomicPairRDD
or something like that.What type should a join return? How should we handle subsequent joins on a joined
GenomicRDD
?The text was updated successfully, but these errors were encountered: