cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Holmberg (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10390) inconsistent quoted identifier handling in UDTs
Date Fri, 30 Oct 2015 17:08:27 GMT


Adam Holmberg commented on CASSANDRA-10390:

[PYTHON-413|] is in driver master. Will
be merged with when we commit CASSANDRA-10513. If you want to resolve this independently I
can find the commit for you, but I assumed we would want to minimize driver updates and just
let it happen with the above.

> inconsistent quoted identifier handling in UDTs
> -----------------------------------------------
>                 Key: CASSANDRA-10390
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>         Environment: 2.2.1
>            Reporter: Jonathan Halliday
>            Assignee: Sam Tunnicliffe
>             Fix For: 2.2.x
> > create keyspace test with replication = {'class': 'SimpleStrategy', 'replication_factor':
1 } ;
> > create type if not exists mytype ("my.field" text);
> > desc keyspace; -- observe that mytype is listed
> > create table mytable (pk int primary key, myfield frozen<mytype>);
> > desc keyspace; -- observe that mytype is listed, but mytable is not.
> > select * from mytable;
> ValueError: Type names and field names can only contain alphanumeric characters and underscores:
> create table myothertable (pk int primary key, "my.field" text);
> select * from myothertable; -- valid
> huh? It's valid to create a field of a table, or a field of a type, with a quoted name
containing non-alpha chars, but it's not valid to use a such a type in a table?  I can just
about live with that though it seems unnecessarily restrictive, but allowing creation of such
a table and then making it invisible/unusable definitely seems wrong.

This message was sent by Atlassian JIRA

View raw message