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

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.2.0
• Component/s: SparkR
• Target Version/s: 2.2.0
• Assignee: Hyukjin Kwon
• Reporter: Hyukjin Kwon
• Created: 09/Oct/16 06:55
• Updated: 12/Dec/22 18:11
• Resolved: 20/Dec/16 13:46

Description

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

Issue Links

• links to: [Github] Pull Request #15608 (HyukjinKwon)