CLI should not start up if server is down #360
Labels
Comments
|
FYI: Also tracked internally under ticket 358. |
rodesai
added a commit
that referenced
this issue
Dec 13, 2017
The goal here is to provide more useful error messaging in the cli. This includes more informative messages for certain errors, and leveraging exception causes to provide more info: * Add a CommonUtils class for common utility methods. Currently, this includes methods for printing error messages that can include information about the errors/exceptions that caused the exception for which a message is being generated. * Print a more visible warning if the ksql server cannot be contacted when the cli is started in remote mode. * Wrap rest client errors in a new exception class KsqlRestClientException, and provide a more context-specific error message. Fixes #360
|
Fixed by #514 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was playing with the Docker Demo. I forgot the start the KSQL Server and did log into CLI directly. After doing the first command, I got
This error is not optimal -- even if I immediately realized that the server was not running. (1) the error message can be improved (2) maybe the CLI should not even start up if the server is down in the first place.
The same happens, if Confluent Platform is not started up yet. (3) There should be different error messages for different services that are not available.
The text was updated successfully, but these errors were encountered: