You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2012/11/15 17:04:12 UTC

[jira] [Commented] (CASSANDRA-4177) Little improvement on the messages of the exceptions thrown by ExternalClient

    [ https://issues.apache.org/jira/browse/CASSANDRA-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498088#comment-13498088 ] 

Brandon Williams commented on CASSANDRA-4177:
---------------------------------------------

This patch isn't really going to solve anything for you, except remove the "Could not retrieve endpoint ranges" prefix, which is still technically correct.
                
> Little improvement on the messages of the exceptions thrown by ExternalClient
> -----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-4177
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4177
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Michał Michalski
>            Assignee: Michał Michalski
>            Priority: Trivial
>         Attachments: trunk-4177.txt
>
>
> After adding BulkRecordWriter (or actually ExternalClient) the ability to make use of authentication I've noticed that exceptions that are thrown on login failure are very misguiding - there's always a "Could not retrieve endpoint ranges" RuntimeException being thrown, no matter what really happens. This "hides" the real reason of all authentication problems. I've changed this line a bit, so all the messages are passed without any change, so now I get - for example - "AuthenticationException(why:Given password in password mode MD5 could not be validated for user operator)" or - in worst case - "Unexpected authentication problem", which is waaay more helpful, so I submit this trivial, but useful improvement.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira