[ https://issues.apache.org/jira/browse/CASSANDRA-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060151#comment-13060151 ]
Rick Shaw commented on CASSANDRA-2859: -------------------------------------- Tighter requirements are *better*. WFM. I am shuffling _where_ the checks happen, and will incorporate these fixes in a proposed and rebased patch. Checks are moving to static methods in {{Utils}} and out of {{CassandraConnection}} and {{CassandraDriver}}. > JDBC connection should catch malformed URLs better > -------------------------------------------------- > > Key: CASSANDRA-2859 > URL: https://issues.apache.org/jira/browse/CASSANDRA-2859 > Project: Cassandra > Issue Type: Improvement > Components: Drivers > Reporter: Jonathan Ellis > Assignee: Jonathan Ellis > Attachments: 2859.txt > > > Some problems with the current connection handing: > - host-less URLs are assumed to be localhost, when this is more commonly the > result of a malformed URL (exhibit A: the current JdbcDriverTest connection) > - there is no standard syntax for user/password in the url; attempting to > support this will result in more malformed URLs. most (all?) other JDBC > drivers force you to use the user/pass or properties constructors instead. > - finally, a malformed URL can result in a very confusing > InvalidRequestException if you manage to end up with garbage in the "path" > component (which becomes keyspace): we send USE X to the server and if there > are non-alphanumeric characters there we will get back a cryptic antlr parse > failure ("line 1:28 no viable alternative at character 'K'") -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira