[GitHub] [spark] shahidki31 opened a new pull request #24531: [SPARK-27636][MLLIB]Remove cached RDD blocks after PIC execution

Sun, 05 May 2019 15:14:09 -0700 

shahidki31 opened a new pull request #24531: [SPARK-27636][MLLIB]Remove cached 
RDD blocks after PIC execution
URL: https://github.com/apache/spark/pull/24531
 
 
   ## What changes were proposed in this pull request?
   
   Test steps to reproduce:
   
   1) bin/spark-shell
   ```
   val dataset = spark.createDataFrame(Seq(
                                       (0L, 1L, 1.0),
                                       (1L,2L,1.0),
                                       (3L, 4L,1.0),
                                       (4L,0L,0.1))).toDF("src", "dst", 
"weight")
   
   val model = new PowerIterationClustering().
                              setMaxIter(10).
                              setInitMode("degree").
                             setWeightCol("weight")
   
   val prediction = model.assignClusters(dataset).select("id", "cluster")
   ```
   
   2) Open storage tab of the UI. We can see many RDD block cached, even after 
running the PIC.
   
   
   ## How was this patch tested?
   Manually tested and existing UTs.
   Before patch:
   ![Screenshot from 2019-05-06 
02-53-45](https://user-images.githubusercontent.com/23054875/57201033-daf61b80-6fb0-11e9-97ff-7534909ce2d3.png)
   
   After patch:
   ![Screenshot from 2019-05-06 
03-41-04](https://user-images.githubusercontent.com/23054875/57201043-07aa3300-6fb1-11e9-855b-f63ee18ea371.png)
   
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to