Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/20770
@ajithme so have you got some time to recheck?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/20770
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user squito commented on the issue:
https://github.com/apache/spark/pull/20770
took a quick look, agree with shivaram's observations, you've got to handle
`shuffleIdToMapStage` which will not be so easy.
---
Github user AjithShetty2489 commented on the issue:
https://github.com/apache/spark/pull/20770
@shivaram yes, you are right. Let me recheck
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For
Github user AjithShetty2489 commented on the issue:
https://github.com/apache/spark/pull/20770
@Ngone51 Thanks for the question. I am not quite sure of actual
implementation of Triemap but i see
https://www.scala-lang.org/api/2.12.3/scala/collection/concurrent/TrieMap.html
Github user markhamstra commented on the issue:
https://github.com/apache/spark/pull/20770
@squito is the master of DAGSchedulerSuite, and can provide you the best
advice on changing or adding to the existing DAGSchedulerSuite. I'll be back
from skiing next week and try to find some
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/20770
@AjithShetty2489 I'm not sure just changing these two maps is sufficient ?
For example createResultStage could in turn create all the parent stages and
the parents stages could be ShuffleMapStage
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/20770
cc @kayousterhout @markhamstra
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands,
Github user AjithShetty2489 commented on the issue:
https://github.com/apache/spark/pull/20770
For UT, i see DAGSchedulerSuite currently does not have same behaviour as
DAGScheduler as its events posted to DAGSchedulerEventProcessLoopTester are
running in same thread unlike
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/20770
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/20770
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
11 matches
Mail list logo
