diff options
| author | Davies Liu <davies.liu@gmail.com> | 2014-09-12 19:05:39 -0700 |
|---|---|---|
| committer | Josh Rosen <joshrosen@apache.org> | 2014-09-12 19:05:39 -0700 |
| commit | 885d1621bc06bc1f009c9707c3452eac26baf828 (patch) | |
| tree | 56cf101d515a6bc70abf0f721d10722ecad866fa /tox.ini | |
| parent | 71af030b46a89aaa9a87f18f56b9e1f1cd8ce2e7 (diff) | |
| download | spark-885d1621bc06bc1f009c9707c3452eac26baf828.tar.gz spark-885d1621bc06bc1f009c9707c3452eac26baf828.tar.bz2 spark-885d1621bc06bc1f009c9707c3452eac26baf828.zip | |
[SPARK-3500] [SQL] use JavaSchemaRDD as SchemaRDD._jschema_rdd
Currently, SchemaRDD._jschema_rdd is SchemaRDD, the Scala API (coalesce(), repartition()) can not been called in Python easily, there is no way to specify the implicit parameter `ord`. The _jrdd is an JavaRDD, so _jschema_rdd should also be JavaSchemaRDD.
In this patch, change _schema_rdd to JavaSchemaRDD, also added an assert for it. If some methods are missing from JavaSchemaRDD, then it's called by _schema_rdd.baseSchemaRDD().xxx().
BTW, Do we need JavaSQLContext?
Author: Davies Liu <davies.liu@gmail.com>
Closes #2369 from davies/fix_schemardd and squashes the following commits:
abee159 [Davies Liu] use JavaSchemaRDD as SchemaRDD._jschema_rdd
Diffstat (limited to 'tox.ini')
0 files changed, 0 insertions, 0 deletions