You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Henri DF (JIRA)" <ji...@apache.org> on 2015/12/04 20:06:11 UTC
[jira] [Updated] (SPARK-12150) numPartitions argument to
sqlContext.range() should be optional
[ https://issues.apache.org/jira/browse/SPARK-12150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henri DF updated SPARK-12150:
-----------------------------
Description:
It's a little inconsistent that the first two sqlContext.range() methods don't take a numPartitions arg, while the third one does.
And more importantly, it's a little inconvenient that the numPartitions arg is mandatory for the third range() method - it means that if you want to specify a step, you suddenly have to think about partitioning - an orthogonal concern.
My suggestion would be to make numPartitions optional, like it is on the sparkContext.range(..).
was:
When using the various sqlContext.range(..) functions,
It's a little inconsistent that the first two sqlContext.range() methods don't take a numPartitions arg, while the third one does.
And more importantly, it's a little inconvenient that the numPartitions arg is mandatory for the third range() method - it means that if you want to specify a step, you suddenly have to think about partitioning - an orthogonal concern.
My suggestion would be to make numPartitions optional, like it is on the sparkContext.range(..).
> numPartitions argument to sqlContext.range() should be optional
> ----------------------------------------------------------------
>
> Key: SPARK-12150
> URL: https://issues.apache.org/jira/browse/SPARK-12150
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Reporter: Henri DF
> Priority: Minor
>
> It's a little inconsistent that the first two sqlContext.range() methods don't take a numPartitions arg, while the third one does.
> And more importantly, it's a little inconvenient that the numPartitions arg is mandatory for the third range() method - it means that if you want to specify a step, you suddenly have to think about partitioning - an orthogonal concern.
> My suggestion would be to make numPartitions optional, like it is on the sparkContext.range(..).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org