You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Yin Huai (JIRA)" <ji...@apache.org> on 2015/05/27 05:25:17 UTC
[jira] [Resolved] (SPARK-7858) DataSourceStrategy.createPhysicalRDD
should use output schema when performing row conversions, not relation
schema
[ https://issues.apache.org/jira/browse/SPARK-7858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yin Huai resolved SPARK-7858.
-----------------------------
Resolution: Fixed
Fix Version/s: 1.4.0
Issue resolved by pull request 6400
[https://github.com/apache/spark/pull/6400]
> DataSourceStrategy.createPhysicalRDD should use output schema when performing row conversions, not relation schema
> ------------------------------------------------------------------------------------------------------------------
>
> Key: SPARK-7858
> URL: https://issues.apache.org/jira/browse/SPARK-7858
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 1.4.0
> Reporter: Josh Rosen
> Assignee: Josh Rosen
> Priority: Critical
> Fix For: 1.4.0
>
>
> In {{DataSourceStrategy.createPhysicalRDD}}, we use the relation schema as the target schema for converting incoming rows into Catalyst rows. However, we should be using the output schema instead, since our scan might return a subset of the relation's columns.
--
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