Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15231
@felixcheung I see. Yes, I think that is a good idea. I just read the codes
further. How about the one like the original message before such as ..
```
Error in invokeJava(isStatic = TRUE, className, methodName, ...): illegal
argument - Invalid type unknown
```
for now and then dealing with printing the original name (`getSQLDataType`)
in the future PR which I will submit (which we taked in
https://github.com/apache/spark/pull/15231#discussion_r80594580)?
It seems one of the easy ways to reach the goal would be a wrapper for
`callJMethod` and treating them in a single place with `captureJVMException`.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
