[jira] [Resolved] (SPARK-17838) Strict type checking for arguments with a better messages across APIs.

["Felix Cheung (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-17838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Cheung resolved SPARK-17838.
----------------------------------
          Resolution: Fixed
            Assignee: Hyukjin Kwon
       Fix Version/s: 2.2.0
    Target Version/s: 2.2.0

> Strict type checking for arguments with a better messages across APIs.
> ----------------------------------------------------------------------
>
>                 Key: SPARK-17838
>                 URL: https://issues.apache.org/jira/browse/SPARK-17838
>             Project: Spark
>          Issue Type: Improvement
>          Components: SparkR
>            Reporter: Hyukjin Kwon
>            Assignee: Hyukjin Kwon
>             Fix For: 2.2.0
>
>
> It seems there should be more strict type checking for arguments in SparkR APIs. This was discussed in several PRs. 
> https://github.com/apache/spark/pull/15239#discussion_r82445435
> Roughly it seems there are three cases as below:
> The first case below was described in https://github.com/apache/spark/pull/15239#discussion_r82445435
> - Check for {{zero-length variable name}}
> Some of other cases below were handled in https://github.com/apache/spark/pull/15231#discussion_r80417904
> - Catch the exception from JVM and format it as pretty
> - Check strictly types before calling JVM in SparkR



--
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