You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Cheng Lian (JIRA)" <ji...@apache.org> on 2016/01/24 03:19:39 UTC
[jira] [Commented] (SPARK-12624) When schema is specified, we
should give better error message if actual row length doesn't match
[ https://issues.apache.org/jira/browse/SPARK-12624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114123#comment-15114123 ]
Cheng Lian commented on SPARK-12624:
------------------------------------
Quoted Davies' offline comment
{quote}
We always raise a exception in 1.4/1.5, different exception in 1.6/master, (the show() of 1.6.0 is weird, don't know why).
We should raise a better exception when deserializing them in JVM (EvaluatePython.fromJava).
{quote}
> When schema is specified, we should give better error message if actual row length doesn't match
> ------------------------------------------------------------------------------------------------
>
> Key: SPARK-12624
> URL: https://issues.apache.org/jira/browse/SPARK-12624
> Project: Spark
> Issue Type: Bug
> Components: PySpark, SQL
> Reporter: Reynold Xin
> Priority: Blocker
>
> See https://github.com/apache/spark/pull/10564
> Basically that test case should pass without the above fix and just assume b is null.
--
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