[ https://issues.apache.org/jira/browse/CASSANDRA-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908724#comment-14908724 ]
Sam Tunnicliffe edited comment on CASSANDRA-10390 at 9/25/15 9:48 PM: ---------------------------------------------------------------------- This is a python driver bug, types like the one described are legal & can in fact be accessed using the java driver. I've opened [PYTHON-413|https://datastax-oss.atlassian.net/browse/PYTHON-413] and we'll need to update the bundled driver once that's resolved. was (Author: beobal): This is a python driver bug, types like the one described are legal & can in fact be accessed using the java driver. I've opened [https://datastax-oss.atlassian.net/browse/PYTHON-413|PYTHON-413] and we'll need to update the bundled driver once that's resolved. > inconsistent quoted identifier handling in UDTs > ----------------------------------------------- > > Key: CASSANDRA-10390 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10390 > Project: Cassandra > Issue Type: Bug > 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: 'my.field' > 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 (v6.3.4#6332)