[jira] [Commented] (SPARK-16797) Repartiton call w/ 0 partitions drops data

2016-07-30 Thread Dongjoon Hyun (JIRA) 

[ 
https://issues.apache.org/jira/browse/SPARK-16797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400542#comment-15400542
 ] 

Dongjoon Hyun commented on SPARK-16797:
---

Oh, I see. Never mind, [~bjeffrey].

> Repartiton call w/ 0 partitions drops data
> --
>
> Key: SPARK-16797
> URL: https://issues.apache.org/jira/browse/SPARK-16797
> Project: Spark
>  Issue Type: Bug
>  Components: Spark Core
>Affects Versions: 1.6.2
>Reporter: Bryan Jeffrey
>Priority: Minor
>  Labels: easyfix
> Fix For: 2.0.0
>
>
> When you call RDD.repartition(0) or DStream.repartition(0), the input data 
> silently dropped. This should not silently fail; instead an exception should 
> be thrown to alert the user to the issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

[jira] [Commented] (SPARK-16797) Repartiton call w/ 0 partitions drops data

2016-07-29 Thread Bryan Jeffrey (JIRA) 

[ 
https://issues.apache.org/jira/browse/SPARK-16797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400362#comment-15400362
 ] 

Bryan Jeffrey commented on SPARK-16797:
---

I just ran the same thing on Spark 2.0.0 as released, and the issue does appear 
to be resolved.  I'm sorry about the confusion - I had run this earlier on a 
2.0 preview & thought I was seeing the same issue.  We can close this as fixed 
in 2.0.0

Thank you!

> Repartiton call w/ 0 partitions drops data
> --
>
> Key: SPARK-16797
> URL: https://issues.apache.org/jira/browse/SPARK-16797
> Project: Spark
>  Issue Type: Bug
>  Components: Spark Core
>Affects Versions: 1.6.2, 2.0.0
>Reporter: Bryan Jeffrey
>Priority: Minor
>  Labels: easyfix
>
> When you call RDD.repartition(0) or DStream.repartition(0), the input data 
> silently dropped. This should not silently fail; instead an exception should 
> be thrown to alert the user to the issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

[jira] [Commented] (SPARK-16797) Repartiton call w/ 0 partitions drops data

2016-07-29 Thread Bryan Jeffrey (JIRA) 

[ 
https://issues.apache.org/jira/browse/SPARK-16797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400356#comment-15400356
 ] 

Bryan Jeffrey commented on SPARK-16797:
---

Hello. Here is a simple example using Spark 1.6.1:

[jira] [Commented] (SPARK-16797) Repartiton call w/ 0 partitions drops data

2016-07-29 Thread Dongjoon Hyun (JIRA) 

[ 
https://issues.apache.org/jira/browse/SPARK-16797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399948#comment-15399948
 ] 

Dongjoon Hyun commented on SPARK-16797:
---

Hi, [~bjeffrey].
Could you give me more information how to find that? For me, it seems to raise 
a proper exception like the following.
{code}
scala> spark.sparkContext.parallelize(1 to 10).repartition(0)
java.lang.IllegalArgumentException: requirement failed: Number of partitions 
(0) must be positive.
{code}

> Repartiton call w/ 0 partitions drops data
> --
>
> Key: SPARK-16797
> URL: https://issues.apache.org/jira/browse/SPARK-16797
> Project: Spark
>  Issue Type: Bug
>  Components: Spark Core
>Affects Versions: 1.6.2, 2.0.0
>Reporter: Bryan Jeffrey
>Priority: Minor
>  Labels: easyfix
>
> When you call RDD.repartition(0) or DStream.repartition(0), the input data 
> silently dropped. This should not silently fail; instead an exception should 
> be thrown to alert the user to the issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org