You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (Jira)" <ji...@apache.org> on 2022/07/05 02:50:00 UTC
[jira] [Updated] (SPARK-39602) Invoking .repartition(100000) in a unit test causes the unit test to take >20 minutes.
[ https://issues.apache.org/jira/browse/SPARK-39602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon updated SPARK-39602:
---------------------------------
Issue Type: Improvement (was: Bug)
> Invoking .repartition(100000) in a unit test causes the unit test to take >20 minutes.
> --------------------------------------------------------------------------------------
>
> Key: SPARK-39602
> URL: https://issues.apache.org/jira/browse/SPARK-39602
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 3.3.0
> Reporter: Tanin Na Nakorn
> Priority: Major
>
> Here's a proof of concept:
> {code}
> val result = spark
> .createDataset(List("test"))
> .rdd
> .repartition(100000)
> .map { _ =>
> "test"
> }
> .collect()
> .toList
>
> println(result)
> {code}
> This code takes a very long time in unit test.
> We aim to test for correctness in unit test... not testing the repartition.
> Is there a way to make it faster? (e.g. disable partition in test)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org