[CASSANDRA-2859] JDBC connection should catch malformed URLs better

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Duplicate
• Assignee: Unassigned
• Reporter: Jonathan Ellis
• Created: 05/Jul/11 20:48
• Updated: 16/Apr/19 09:32
• Resolved: 20/Jul/11 03:27

Description

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'")

Issue Links

• is related to: CASSANDRA-2924 Consolidate JDBC driver classes: Connection and CassandraConnection in advance of feature additions for 1.1