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

Closed
devin-petersohn opened this Issue Jun 21, 2017 · 0 comments

Comments

Projects
2 participants
@devin-petersohn
Member

devin-petersohn commented Jun 21, 2017

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 extends GenomicRDD, 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 the PairRDDFunctions in Spark. I don't see it as a problem for the user to be exposed to a GenomicPairRDD or something like that.

What type should a join return? How should we handle subsequent joins on a joined GenomicRDD?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment