New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

improved error handing #54

Closed
snowch opened this Issue Jul 28, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@snowch
Contributor

snowch commented Jul 28, 2016

When an error is thrown by stocator, it is very difficult to find the cause of the error. For example:

Py4JJavaError: An error occurred while calling z:org.apache.spark.api.python.PythonRDD.collectAndServe.
: java.lang.NullPointerException
    at org.javaswift.joss.client.impl.ClientImpl.createAccount(ClientImpl.java:100)
    at org.javaswift.joss.client.impl.ClientImpl.createAccount(ClientImpl.java:27)
        ...

Stocator is quite difficult to work with because the error messages generally don't help you identify the root cause of the problem.

@gilv

This comment has been minimized.

Show comment
Hide comment
@gilv

gilv Jul 28, 2016

Contributor

@snowch in general, Stocator provides many info when exception happens.
Can you show the whole trace? The exception you copy-paste here is from JOSS on create account.. this might happen when some auth related information is missing.
I need to see the whole flow, perhaps some scenarios in Stocator need better exception handling and provide better information.

Contributor

gilv commented Jul 28, 2016

@snowch in general, Stocator provides many info when exception happens.
Can you show the whole trace? The exception you copy-paste here is from JOSS on create account.. this might happen when some auth related information is missing.
I need to see the whole flow, perhaps some scenarios in Stocator need better exception handling and provide better information.

@gilv gilv closed this Aug 16, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment