spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glenn Weidner (JIRA)" <>
Subject [jira] [Commented] (SPARK-6290) bug upon error
Date Thu, 23 Apr 2015 01:01:39 GMT


Glenn Weidner commented on SPARK-6290:

I would like to work on this.  In a test scenario created to force the error, observed the
first part of the message was helpful in describing the failure due to types not matching
and included the required vs. actual type information.  However, the second part of the message
contained a java.lang.IllegalArgumentException embedded with stack trace.  For example:

java.lang.IllegalArgumentException: requirement failed: 
	at scala.Predef$.require(Predef.scala:233)

Can you confirm the exception stack trace part is the "weird" error referred to in the description?

> bug upon error
> -----------------------------------------------------
>                 Key: SPARK-6290
>                 URL:
>             Project: Spark
>          Issue Type: Bug
>          Components: ML
>    Affects Versions: 1.3.0
>            Reporter: Joseph K. Bradley
>            Priority: Minor
> In checkInputColumn, if data types do not match, it tries to print an error message with
this in it:
> {code}
> Column param description: ${getParam(colName)}"
> {code}
> However, getParam cannot be called on the string colName; it needs the parameter name,
which this method is not given.  This causes a weird error which users may find hard to understand.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message