Joseph E. Gonzalez
Joseph E. Gonzalez
Hmm, is that error in the master branch? Those line numbers don't seem to "line-up." I guess for now maybe it makes sense to merge #51 since it is simpler.
The current justification for two separate strategies is that the join operation is "light weight" and so recomputing it would not be costly. Alternatively, the mapValues operation could be arbitrarily...
We should also add an RMat graph generator. See http://www.cs.cmu.edu/~christos/PUBLICATIONS/siam04.pdf for details.
Did we ever find a location to place this code?
This github "bug/feature" is getting a little confusing. So is this issue closed? As far as I can tell the generator code has been written but possibly not tested?
This function is actually pretty challenging given that an invocation of: ``` scala g.contractEdges(x => true, _.srcAttr, (a,b) => a) ``` computes connected components.
Did we resolve this issue?
This is still a prototype but I wanted to open the discussion on the design so I can incorporate feedback early.
I have made some organizational changes based on suggestions from @rxin and @mateiz. To RDD I added: ``` scala def pairRDDFunctions[K, V]( implicit t: T
In response to @mridulm, the IndexedRDD exploits the partitioning of the index. If both RDDs are indexed (IndexedRDDs) and have the same index then both must be partitioned identically and...